-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
FeatureRequest: decrypt encrypted text elements during import .enex #543
Comments
Yihaa, thank you for reporting me this issue and to let me improve Yarle! |
+1, such a feature would be greatly helpful, perhaps a 1 or more inputs to fill in the encryption password(s) and Yarle would try to try each of them when trying to decrypt the content. However, am not sure about the private encryption key Evernote uses, not sure if we can find it anywhere |
Official Information from Evernote can be found here: https://help.evernote.com/hc/en-us/articles/208314128-What-type-of-encryption-does-Evernote-use- |
Hi @MichaelHeydukFraba , @Code-Curious , Decryption is now supported: https://github.com/akosbalasko/yarle/releases/tag/v6.4.1 |
I've used this successfully in the past when importing my evernote notes to logseq. I tried today, however, for importing to Obsidian, and it doesn't seem to have an effect. The note is encrypted when importing to Obsidian, and i don't see any mention of an attempt to decrypt in the output log. |
I have lots of passwords in my Evernote .enex file. All are locally encrypted passwords with the Evernote encrypt-Text-Feature.
It would be great if I could specify a local password in the Import Settings, so that the enex-importer decrypts all encrypted texts.
Thanks a lot.
The text was updated successfully, but these errors were encountered: