4 ms·
What you're missing is the proposal to have the email provider generate public key/private key pairs and somehow communicate that detail to the email client. (P
by jcranmer 10y ago
What you're missing is the proposal to have the email provider generate public key/private key pairs and somehow communicate that detail to the email client. (Presumably via some IMAP or POP query?). The current IETF drafts have no provision for how to communicate public keys and private keys to the email provider.
I'll also point out that S/MIME 3.1 lets you encrypt message headers by including an entire message/rfc822 inside an encrypted section. I don't think any email client actually supports doing anything reasonable about that.
- EmilStenstrom 10y agoTrue, I've not included a specification for doing that.
- md_ 10y agoI wasn't aware of that, but of course the destination is still leaked via RCPT. If the server is going to provision keys (and presumably thus escrow them), this is strictly less private than using server-to-server encryption.