@Louis_Kirsch
Tested with success. Here are my input though I think you might have already captured them in your todo list.
Could not decryptâThanks Chiang!
I guess with password change you refer to re-encryption of all data with the new password? This will be tricky to do with the current system â I have to think about how to do this.
What do you mean by password reset?
Same here, sounds great but will need a lot more meddling with the Dynalist code which could turn out to be tricky. Maybe @Shida has ideas how to do this easily.
Yes thatâs right and I donât think I can do anything about this because as you said â the plugin is off. What you can do though if you encounter âcould not decryptâ is go into your version history and undo the accidental change.
Yes. Say I decided to change password to a stronger one, I was hoping the extension performs updating all existing encrypted text prior to password change, to match the latest password.
A good point!
Itâs tricky because in order to make it secure I would have to copy all your documents in order to discard the version history. In principle I could do that using the API - but it will be a bit of work.
@CHIANG_E @Steffen I have updated the interface
As usual the update is on github https://github.com/timediv/DynaCrypt/releases/tag/1.1
https://github.com/timediv/DynaCrypt/releases/tag/1.2
I updated, but now i cant decrypt my lists anymore. the new ones
Yes I had to upgrade the encryption algorithm. I hope this wonât be necessary again but during these initial stages I have to make sure there are no vulnerabilities.
You can use the old version to save your document as opml or copy the data. Then insert it with the new plug in version.
Guess DC1.2 has somewhat solved performance of 1.1.
Anyway, I tested both, with none of the 1.0-1.2 unloaded.
Okay, testing of 1.1 (activated alone): I was required to reenter my password.
Testing of 1.2 (activated alone): Password needed no re-enter. Duplication of encrypted nodes retained the encryption status.
Love the padlocks. Is 1.2 final for pre-release?
Risk assessment: In what circumstances could the encryption be unrecoverable, other than lost of password and âtamperedâ encrypted nodes (as in my previous reply)?
I think it is quite stable now. There are still a few features missing for convenience, but it certainly is usable already:
In principle you could always recover by using an old version of the plugin / running the js decryption manually on one of your backup files or downloaded opmls. I think there are two modes of inconvenience that could happen
@Louis_Kirsch
Appreciate your time and efforts, keep the forum posted please. Also some level of documentation such as recovery guide at the Github (?) would be nice and life-saver.
Thatâs a good idea. I might just add a script that takes the encrypted backup files and outputs an unencrypted backup for Dynalist independent recovery.
Yes!
Wish that it could auto download the working Dynalist document (my guess) in multiple opml files at fixed intervals in the background, given that there is no control over when the user will turn off CRX (assuming selective encryption) or even close the browser. File names to have date-time stamps & doc name.
Iâm not entirely sure what you are asking for. Can you please clarify?
Dynalist has a backup feature already which you can access in the menu or setup auto backups. These backups will be encrypted (as they are downloads directly from the server) so it would be useful to have an additional option in the extension to decrypt such a backup independent of whether the extension still works for Dynalist (as Dynalist might go down at some point or otherwise make the extension incompatible).
When you export a file to opml within Dynalist (not the backup feature) then you actually get the unencrypted copy that the client has in-memory.
That was functionality I wish you could add to the script in the reply from you earlier:
script that takes the encrypted backup files and outputs an unencrypted backup for Dynalist independent recovery
I need the script to download the âunencrypted backupâ (i assumed opml file) at an interval say every 5 mins.
EDIT:
I guess my request is not valid when âthe scriptâ component of DynaCrypt is capable of decrypting the Dynalist routine-backup (local copy downloaded from GDrive/Dropbox; encrypted) in OFFLINE mode.
Yes I think we shouldnât reinvent the backup mechanism, just allow the encrypted backups to be decrypted offline without relying on Dynalist.
Wait is this version history a hidden feature of DynaList?
Itâs a Dynalist Pro feature - right click the document
Pointless semantics but, is this âend-to-end encryptionâ if both ends are one in the same? Or is it just âencryptionâ? All encryption has one decrypt end. I think of end-to-end as Signal app, 2+ people, so the title confused me making me think the other end was dynalists AWS storage, decrypted in plain text, and it only encrypted the transit, because how else would it be âend-to-endâ but nevermind thatâs not the case. Cool nonetheless. Anything to get corporate jobs to accept dynalist into their high security IT whitelists is nice.
Thanks for the feedback! You are right âclient side encryptionâ or so might be a better description.
Wow!
But I sadly canât risk my data. So external vetting is important to me. But this is a really nice plugin. Thanks for all the work.
