3 ms·

> When I first installed Signal it didn't have Sealed Sender, which means that an adversary in Signal's privileged position knows who is sending me messages (to

> When I first installed Signal it didn't have Sealed Sender, which means that an adversary in Signal's privileged position knows who is sending me messages (today only I know who is sending me messages) by only looking at the message... but: you authenticate yourself at the Signal service and you use your authentication to drop of a set of messages How do they not know who sent them (if they want to know)?

tialaramex 5y ago
You don't need to identify yourself to Signal in order to send messages with Sealed Sender. You just present a delivery token, which proves you are authorised to send messages to this recipient, and your encrypted message addressed to the recipient. Signal doesn't learn who sent it nor do they care, the recipient's client figures out who sent it after decrypting it.
- kitkat_new 5y ago
  > You just present a delivery token, which proves you are authorised to send messages to this recipient, and your encrypted message addressed to the recipient. And how do you get it? > Signal doesn't learn who sent it nor do they care, the recipient's client figures out who sent it after decrypting it. which doesn't mean they couldn't
  - brewmarche 5y ago
    I don’t know Signal internals but it could work like this: First message without sealed sender from A to B: Signal knows the recipient. This messages includes a token that A wants to receive B’s messages with sealed sender, that is, a payload signed with A’s private key B accepts message and also sends back proof that it wants to received further messages from A with sealed sender (again something signed by B). This message can be sent via sealed sender as well because B now has A’s token Signal Server only allows sealed sender if token is valid (i.e. is signed by the recipient)
    - brewmarche 5y ago
      E: Just realised I have made a mistake when typing, sorry. In the first message Signal knows the sender. Signal always knows the recipient (otherwise it couldn’t deliver). From then on Signal doesn’t know the senders because of Sealed Sender. Also: “a token that A wants” should have been “a token indicating that A wants”

tialaramex 5y ago

You don't need to identify yourself to Signal in order to send messages with Sealed Sender. You just present a delivery token, which proves you are authorised to send messages to this recipient, and your encrypted message addressed to the recipient. Signal doesn't learn who sent it nor do they care, the recipient's client figures out who sent it after decrypting it.

kitkat_new 5y ago
> You just present a delivery token, which proves you are authorised to send messages to this recipient, and your encrypted message addressed to the recipient. And how do you get it? > Signal doesn't learn who sent it nor do they care, the recipient's client figures out who sent it after decrypting it. which doesn't mean they couldn't
- brewmarche 5y ago
  I don’t know Signal internals but it could work like this: First message without sealed sender from A to B: Signal knows the recipient. This messages includes a token that A wants to receive B’s messages with sealed sender, that is, a payload signed with A’s private key B accepts message and also sends back proof that it wants to received further messages from A with sealed sender (again something signed by B). This message can be sent via sealed sender as well because B now has A’s token Signal Server only allows sealed sender if token is valid (i.e. is signed by the recipient)
  - brewmarche 5y ago
    E: Just realised I have made a mistake when typing, sorry. In the first message Signal knows the sender. Signal always knows the recipient (otherwise it couldn’t deliver). From then on Signal doesn’t know the senders because of Sealed Sender. Also: “a token that A wants” should have been “a token indicating that A wants”