decryption #47
Labels
No Label
DBF
Dates
Defined Names
Features
Formula
HTML
Images
Infrastructure
Integration
International
ODS
Operations
Performance
PivotTables
Pro
Protection
Read Bug
SSF
SYLK
Style
Write Bug
good first issue
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sheetjs/sheetjs#47
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I don't see support for decrypting password-protected spreadsheets. Is this feature beyond the scope of this library?
Is there a way to programmatically decrypt spreadsheets? Doesn't need to be JS.
@surjikal I'm sitting on a unmerged patch to support password encryption (FF is triggering "out of memory" errors, which is why I haven't merged it yet). If this is something you'd like to see sooner rather than later, I can prioritize it.
In the interim, it appears that the Java library POI (https://poi.apache.org/encryption.html) supports password protection
Very cool! Right now, I'd only need this for node, so the FF stuff would not affect me. Maybe you could push the change to a separate branch?
Very cool stuff overall. We need the support for reading password-protected spreadsheets for node environment as well. Thanks
@surjikal Any progress on this? Being able to read a password protected xlsx file would be very useful for me. Did the commit above by @clarketm that links to this issue actually impact password/decryption support?
@sgilroy Sorry, I have not looked at the patch above. I posted this issue almost 3 years ago! Thanks for bringing it to my attention though, might be useful someday.
@SheetJSDev Is the patch you referred to back in 2014 https://github.com/SheetJS/js-xlsx/issues/47#issuecomment-35060977 available on a branch or fork somewhere? I'm using js-xlsx in nodejs, so a Firefox memory error would not affect me.
Closing in favor of #774