News for hackers. Stuff that matters.
Re:21 years after the request OpenPGP support gets added to ... by zajio1am on Thursday September 17, 2020 @08:28PM (#24511634)
> and it's ok to leak metadata?

How could Signal (or other client-server protocol) not leak metadata? It is true that OpenPGP leaks more metadata than necessary (e.g. Subject), but seems to me that any efficient message protocol needs to leak at least three most important metadata - source, destination, time.

One could avoid leaking destination by broadcasting encrypted to many receivers (when only the true one can decrypt it) and therefore server does not need to know true destinations, but that is rather inefficient.

Re:21 years after the request OpenPGP support gets added to ... by skyfaller on Thursday September 17, 2020 @08:37PM (#24511695)
Signal has been working on features like "sealed sender", which encrypts the source metadata: https://signal.org/blog/sealed-sender/

I don't know if they can do anything about destination or time, but even hiding the source seems like a significant advancement.

Re:21 years after the request OpenPGP support gets added to ... by JetSpiegel on Saturday September 19, 2020 @10:40PM (#24531590)
How does that even work? The only way to encrypt the sender is to send every (encrypted) message to everyone and let the clients drop the ones they can't encrypt. On a Phone. I hope they give out free batteries.

The post mentions some kind of "short-lived" pseudo-sender, which is vulnerable to the same metadata analysis.

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.