-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
About password protected numbers files #93
Comments
See also #88. The challenge will be that AES-encrypted data is indistinguishable from random noise. It's possible for numbers-parser to unpack the top-level document and spot that it has what looks like Numbers metadata, but no readable IWA files, and infer from this the document might be encrypted. But the only option would be to raise an exception on the |
I noticed that if a numbers file is encrypted, then almost all iwa files in it are unreadable, that is, the iwa binary stream does not start with 0x00 |
The most recent commits on the GitHub main branch include a test for the existence of |
Back to you original question, the answer is Yes. Numbers app can be manipulated by AppleScript, and consequent several Python libraries. For AppleScript, you can check the
Or you can use
Hope this helps. |
The Zip that wraps the document contains some files that are indicative of a password-protected file. There is code in place to check for this (see https://github.com/masaccio/numbers-parser/blob/main/src/numbers_parser/iwork.py#L201) but it's not published yet in a release as I just need to tidy up some code elsewhere to return to 100% coverage. |
According to some information on the Internet, encrypted documents are encrypted using ASE-128. So is there a simpler way to determine whether a numbers document is encrypted? I do not need to parse the content of the encrypted document.
The text was updated successfully, but these errors were encountered: