Is E2EE usefull with WebDAV over SSL ( HTTPS )?

Since you can use WebDAV with SSL ( WebDAV over HTTPS ).
In this case Data in securely encrypted when synchronised between devices.
How does E2EE improve security in this context ?

Your server could still be hacked, bypassing the SSL (which just encrypts the traffic between you and your server).

Joplin encrypts the content itself which will definitely add an extra layer of security.

Thank you @Sophia ! I guess I just didn’t thought about that.
I think the official documentation is a bit blurry official doc

End-to-end encryption (E2EE) is a system where only the owner of the data (i.e. notes, notebooks, tags or resources) can read it. It prevents potential eavesdroppers - including telecom providers, internet providers, and even the developers of Joplin from being able to access the data.

I will propose a pull request to clarify it.
Best regards.

1 Like

SSL is about encryption in transit (between client and server). No one can intercept your data by eavesdropping your connection.

E2EE is about encryption at rest. No one can read your stored data since it is written to disk encrypted. The data is only encrypted locally in memory in the client.