Skip to content
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

Consider saving all the app data and setting using encrypted overlay filesystem #35

Closed
vladimiry opened this issue Jul 18, 2018 · 1 comment

Comments

@vladimiry
Copy link
Owner

all the app data means including stuff that Electron generates in app data folder (you can go to this folder clicking Open Settings Folder app/tray menu item). App strives to avoid persistence of any sensitive data in web related storages (IndexedDB, Cookies, LocalStorage, etc) going with in-memory / default webview persistence mode (in contrast of how for example Rambox does it). This is why app has to login into the email accounts each time being opened. But still, some information saved by Electron in app data folder might be considered as sensitive.

Full app data folder encryption can be done manually of courses, for example, using tools like gocryptfs / cppcryptfs / sirikali, and I guess some users already go with either similar overlay filesystems or full disk encryption. But it would be nice if this app would be capable to mount/unmount encrypted file systems by its own with an already used master password and CLI of the mentioned above gocryptfs/cppcryptfs tools.

For example, having such a feature implemented and undisabable there would be no need to care about enabling encryption explicitly in all the different cases, like keeping a messages database in memory. But even if support of encrypted overlay filesystem will be enabled in this app, it's not going to be undisabable, since it brings a certain level of inconvenience (a need to install additional tools), brings more runtime dependencies, and can be already done by user manually (though using one more password).

@vladimiry
Copy link
Owner Author

Since this can be done already by the user manually, it would be overkill doing this by app. Besides, there is other higher priority things to implement. Closing with won't fix status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant