-
Notifications
You must be signed in to change notification settings - Fork 2
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
Encrypted Email #5
Comments
todd expanded on this as follows by email:
|
There are several attempts to implement #0 currently, notably the Dark Mail Alliance which I see has a client and a server now. So that is well under way. #1, #2 makes sense for outgoing email. Incoming email is probably the most difficult part. We can't check if an |
We can give users an email client that tries to find a key to encrypt all the emails it sends. But, if the user chooses to use a different email client with our email server, we again can't tell if a message they're sending is encrypted before it reaches our server. So again we risk un-encrypted email touching our server. Also, users will probably need to send email to entities that refuse to use gpg or have not yet learned how to use it. So, there's probably no perfect solution for encrypted email. But, we can make it as easy as possible to have it be secure by default. |
Create an encrypted email service.
Initially this should be email + secure auth + built-in-encryption
Later it would be great to have this become a full encryption communication, with sane fall-back to notify the user that their email must be upgraded to communicate encrypted.
The text was updated successfully, but these errors were encountered: