[FEATURE] End to End Encryption

[SilentCoderHere]

💡 Feature-Beschreibung / Feature Description

An option to set a password for the backup, especially for WebDAV.

🎯 Problem / Motivation

This feature will enhance security.

📝 Vorgeschlagene Lösung / Proposed Solution

The app will ask for a password that is used to encrypt the backup file, and the same password will decrypt the file when restoring.

🔄 Alternativen / Alternatives

No response

📱 Plattform / Platform

Android App

⭐ Priorität (aus deiner Sicht) / Priority (from your perspective)

Wichtig / Important

🤝 Beitragen / Contribute

• Ich würde gerne bei der Implementierung helfen / I would like to help with implementation

🔧 Zusätzliche Informationen / Additional Context

No response

[inventory69]

Hi @SilentCoderHere,

Thanks for the suggestion.

I've thought about this and here's my take:

For WebDAV sync, I don't think encryption adds much value. The connection already requires authentication, and you can only restore from the server when you're connected with your credentials anyway. Adding another layer of encryption there would just complicate things without real security benefit.

For local backups though, I can see the point. If someone gets access to your device, unencrypted backup files could be read. That's something I'd consider adding in a future version.

To be clear: the current WebDAV sync doesn't store plaintext passwords or anything sensitive unprotected. The server-side data is protected by your WebDAV credentials.

I'll keep this on the backlog for local backup encryption, it might land in one of the next releases. If you have a specific threat model in mind that I'm missing, let me know.

[SilentCoderHere]

Hi there! 😊

Thanks for the implementation of encrypted local backups.

Maybe I wasn’t able to clearly express what I meant before. I was requesting a feature where the data stored on the server is encrypted, instead of being stored in plain text.

Main content

Server content

I hope this clarifies my request.

Thank you!

[inventory69]

Hello @SilentCoderHere,
indeed it clarifies your request, thank you :)

Yes, E2E encryption is definitely doable! The main challenge is maintaining Markdown desktop compatibility, because AFAIK desktop markdown editors don't have built-in decryption support.

Two options:

1. Toggle: Users choose encryption OR desktop editing
2. Desktop tool: Build a companion app for encrypted note editing

My preference is option 2, since I'm already planning a desktop tool since I started the app, to make desktop integration much simpler. (I am not that happy with the current state as it's not simple enough for our philosophy..)

Important note: This would be true end-to-end encryption (E2E) - notes are encrypted on your device before upload, so only you can decrypt them with your password. The server would only store encrypted data. Notes on your phone could be stored unencrypted (protected by Android's built-in encryption) or optionally encrypted locally as well - that's something we'd need to discuss with the community.

Feel free to open this as a Discussion in the Discussions tab if you'd like - that way others can see it, upvote, and share their thoughts on the implementation approach! This helps me prioritize features based on community interest. 👍

[SamuXzX]

Now I see that:

1. The application assumes a "notes" subfolder
2. Synchronization is not made to make notes on the server being editable here, rather to store them (in .json), with the additional feature (Markdown Desktop Integration) of storing .mds in another folder to actually edit them outside this application

Sorry for having misinterpreted the way the application works. I thought it could be an alternative to Nextcloud Notes, but it seems the scope is something else.