5 ms·
Encrypting the sender is pretty easy. Deliver the encrypted message+sender at the destination. Only the receiver will be able to decrypt it and see who the send
by sobani 6y ago
Encrypting the sender is pretty easy. Deliver the encrypted message+sender at the destination. Only the receiver will be able to decrypt it and see who the sender was.
Encrypting the receiver is a lot harder though. It will probably involve dropping off the message at some central location and some very fancy cryptography. Secure multi-party computation [0] will probably be involved. I don't know if it can be made scalable though.
[0] https://en.wikipedia.org/wiki/Secure_multi-party_computation https://en.wikipedia.org/wiki/Secure_multi-party_computation
- JetSpiegel 6y ago> Encrypting the sender is pretty easy. Deliver the encrypted message+sender at the destination. That's the point. If the sender is encrypted, what's "the destination"? The IPv4 space? A random ID that represents the sender? How does that change the metadata angle?
- sobani 6y agoIf I deliver a bunch of bytes at jet@spiegel.com then that's the destination. Now you can decrypt it with your public key and get `Have a nice day. Regards, sobani` and see that I'm the sender. If I'm worried about leaking my IP address, I can use something like Tor. I'm confused why you think the sender needs to be known in any way to allow bytes to be delivered to your mail server.