-
Notifications
You must be signed in to change notification settings - Fork 258
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
Per-user encryption: Encrypt imap/smtp password with individual user key #1331
Comments
Bump for an old issue. Mailvelope support is a nice start. However, I think it is not unreasonable to implement Autocrypt in NC-Mail. OpenPGP.js exists. It is robust, well tested, audited, and reviewed. I think there should be no need to ask users to install browser extensions in order to gain email encryption. On the other hand, this would require storing a user's PGP private (sub?) key(s) on server, greatly enhancing potential damage of a successful data-exfiltration attack. |
#648 (comment) we closed a similar request because this feature is still way off our roadmap. Would you like to implement and maintain it, though? |
(I didn't find that issue when I searched for existing. Hmm...) I can't code myself out of a bucket, or I just might. Even literal copy-n-paste scripting or coding doesn't seem to work for me. It's super weird and extremely frustrating. For the moment, the NC External Sites feature pointed at a MailPile instance, or other secure email provider (ex: ProtonMail, StartMail) is sufficient and, frankly, superior to installing browser extensions. I just thought that, with at-rest and E2E support implemented, interest in cryptographic function in the greater NextCloud sphere would continue, including the email client. And the SSO feature of the bundle of NC apps is a convenience. To be fair, this type of feature may be less useful to Enterprise customers due to the possible need to keep plaintext email available in an archive for future access requirements by administrators, legal teams and archives, and other users other than the originator (ex: project notes after terminating an employee). However, it might also be useful to Enterprise clients for compliance with HIPAA, or similar legislation, where transmission of certain kinds of data in an encrypted format is required. Would you consider adding it to the Roadmap with a "someday" or "wishlist" tag? |
it really wouldn't make a difference. |
Feature Request
I'd like the Nextcloud mail app to encrypt the stored imap/smtp password with the user's individual key when server-side per-user encryption is enabled. (disabled master key)
To my knowledge the user key never changes, even when the password changes, making this a viable solution.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: