-
Notifications
You must be signed in to change notification settings - Fork 7
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
Nova 3 backup zip is password-protected #9
Comments
Finally figured it out. Double-posting here for posterity, in case anything happens to the above onyx forum post: I sent feedback via the device, and the response was that the notes are encrypted with my "user ID". I didn't know what this was - I had setup dropbox sync and a google account, but the email address associated with either of these didn't work as a decryption key. They later clarified it's "an attribute of your onyx account". To find out your own user ID (which doubles as the encryption key for backed up notes):
I still don't know what the encryption key is when not signed in to an onyx account, the onyx folks claimed that notes are unencrypted when not logged into an onyx account, but that wasn't the case for me. |
@timbertson @bobek Here's a little addendum after a bit of reverse engineering... The password used for backups that are not created in combination with an Onyx account is If this was the only change, we'd just have to add a call to https://docs.python.org/3/library/zipfile.html#zipfile.ZipFile.setpassword while opening it, but it seems (according to #10) that the format has also changed, so there's more work than that... ETA: For future reference in case they decide to change it: |
This is not an issue with your software, but I was hoping maybe you'd know about it. I tried to use this on a backup zip from my new nova 3, but the archive is password-protected.
I posted about it on the boox forums, but no answers so far and I thought maybe you'd have details. I wonder if it's specific to a newer firmware or the nova 3?
The text was updated successfully, but these errors were encountered: