Back to 128bit encryption (in 2.12.15) - really?

ajay · 2023-08-28T06:26:32.287Z

When Joplin went from AES 128bit encryption to AES 256bit, I went through a lot of my notes to make minuscule changes (add a blank), in order to force re-encryption. Today I see that the coming pre-release (2.12.15) will "temporarily" go back to AES 256 because of perceived performance issues. For once, I didn't notice any performance issues (using nextcloud) at all, at least not on a desktop. On the other hand I have declined the above mentioned update, so my notes will remain encrypted with AES 256. Other may have had the same idea.
So why am I reporting this ?
I would just like to indicate that "several" forth and back switches between AES 128 and AES 256 might be less than ideal for some users, regardless of the fact that others report performance problems on slower devices.

laurent · 2023-08-28T09:52:20.071Z

We've added a way to reencrypt all the notes in the next release so the good news is that once we address these performance issues and enable AES-256, you won't have go through all your notes again to reencrypt manually.

FlimFlam · 2023-12-07T21:48:53.714Z

Is there any plan to re-implement aes-256 in the near future? I've stayed on 2.11.11 and don't want to upgrade until aes-256 is re-enabled.

anon55947162 · 2023-12-09T12:50:49.888Z

@FlimFlam have you experienced slow down issue on the mobile app ?

They are services using 256 bit successfully like Cryptomator since years. I don’t understand why Joplin can’t do the same.

The 128 bit could be keep as default option for users with big database or outdated hardware. Then a second option for people with common hardware and 256 bit would be nice.

FlimFlam · 2023-12-09T15:38:01.083Z

Personally I haven't had any issues and android, and I have a pretty large joplin database. I would be fine with being able to select 128/256. Perhaps they haven't done this to keep the experience simple for users?