Yes, that would be better. Encryption isn't free, you lose portability and possibly all your notes if you forget your encryption password. I would like to reserve encryption for just the secret stuff. That is only a small subset of my notes.
I synchronize to a NAS which is attached to the internet. I mainly want to encrypt some notes in case my NAS gets hacked. I would not mind much if the hacker would read my shopping list, I would mind a lot if he would see my passwords.
there is a common disagreement among developers about what E2E means when it comes the the local end.
some developers believe it "ends" when it reaches your box, and that if you want local encryption you should encrypt it yourself on every system you run the client on.
others believe it "ends" on the disk itself.
Dear all,
I just wanted to warn you, as this module seems to have serious security flaw:
- on one computer, enter the note, and encrypt it
- decrypt it again
- synchronize
Open another computer, open the note, and you'll see it is decrypted - the encryption is not persistent. Once the note is decrypted one needs to manually encrypt it again before synchronization. .
Result is, that one might finish with note being encrypted or decrypted on multiple devices in dependence of when synchronization took a place.
I have used this module in order to avoid all of my notes being encrypted. I have thousands of them and on mobile it takes ages to use global e2e encryption. So I have encrypted only sensitive notes, not others. Maybe for others this behaviour is not surprising, but I'm coming from EMACS ORG environment, where all the notes - even the decrypted ones - get encrypted again BEFORE SAVING OF THE DOCUMENT TAKES A PLACE. So it can never happen, that one stores the note unencrypted on the disk.
You might want to report that to his repository as he doesn't seem to be subscribe to this topic