-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add encryption specification #4
Comments
Hello There is no update? I also want this feature. Your project is great and if it had encryption we could easily sync the file with several cloud storage providers. You know, contacts and calendar are very personal and we can't sync them with services like fruux that we don't know who are them and also all data is plain. At least google is better than that but I don't want google and your way is by far great. But if it only had encryption it would be perfect. By the way thank you very much for your great project. Good luck. |
Hello @rustforfuture , One main feature of DecSync is that it can be used with syncthing to syncrhonise folder between different devices. Did you try this ? |
Hello Thanks for your suggestion :) |
This is a must-have feature, please consider adding it! |
But the data in untrusted devices is kept encrypted (see documentation). So you can't really use that data for anything as long as it's encrypted. This would only work if DecSync were able to read that same encrypted format and use the same user-provided password to decrypt it by itself (and encrypt back any modifications). I believe supporting the same encryption specification as Syncthing might work even for those not using Syncthing. Although I'm not sure if it might be messy if a user later wants to migrate their encrypted DecSync folder to Syncthing. |
There is no standard way to encrypt the database. As a result, all applications that have access to the disk can read the data there, even if they don't need to access the database.
This is also required if cloud is used for synchronization, such as Nextcloud, Seafile or Dropbox.
See previous discussion at #3
The text was updated successfully, but these errors were encountered: