News for hackers. Stuff that matters.
Re:21 years after the request OpenPGP support gets added to ... by sobani on Monday September 21, 2020 @04:04AM (#24540917)
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

Re:21 years after the request OpenPGP support gets added to ... by JetSpiegel on Monday September 21, 2020 @07:51PM (#24549601)
> 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?

Re:21 years after the request OpenPGP support gets added to ... by sobani on Tuesday September 22, 2020 @03:58AM (#24552039)
If I deliver a bunch of bytes at [email protected] 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.