3 ms·
It seems like it could be done with a service offering public key info, and using key signing and web-of-trust to keep the keys reliable, and encrypting in open
by Zigurd 13y ago
It seems like it could be done with a service offering public key info, and using key signing and web-of-trust to keep the keys reliable, and encrypting in open source client software not provided or updated by the mail service provider.
That still leaves the service open to being strong-armed into sending you malware. And, of course, your mail headers are in the clear.
But, apparently, to the Lavabit people, what I've outlined here isn't sufficient, and the implication is that the NSA and/or FBI has ways of compromising all email providers no matter how they operate.
- dbond 13y agoThis is why it really needs to be done at the protocol level, an email provider can't change the behavior of my desktop client and the process could be completely automated for the average user.
- Zigurd 13y agoI'm not sure of the relevance of the protocol IF the service remains store-and-forward. Silent Circle and Lavabit seem to think it's better not to use email at all. An open Skype-like system is probably pretty good. Keys are ephemeral, and transferring encrypted files in audio-video sessions makes it hard to MITM.
- dbond 13y agoEmail is pretty bad, but its not going anywhere so we should try to fix it. The service would remain store-and-forward but the content would be encrypted throughout, something which is not currently possible without both parties knowing how to setup and use PGP.