Comment Comment by cakoose Yup, the example doesn't make sense for the reason you pointed out.You could water down the example a bit to make it work:1. Assume there's some other authentication mechanism for client-server communication, e.g. TLS.2. The client sends the user ID unencrypted (within TLS) so the server can route, but encrypts the message contents so the server can't read it.3. The final recipient can validate the message and the user ID.This saves the client from having to send the user ID twice, once in the ciphertext and once in the clear.But another more interesting use case is when you don't even send the associated data: https://news.ycombinator.com/item?id=43827342 parent cakoose 1 year ago
You could water down the example a bit to make it work:
1. Assume there's some other authentication mechanism for client-server communication, e.g. TLS.
2. The client sends the user ID unencrypted (within TLS) so the server can route, but encrypts the message contents so the server can't read it.
3. The final recipient can validate the message and the user ID.
This saves the client from having to send the user ID twice, once in the ciphertext and once in the clear.
But another more interesting use case is when you don't even send the associated data: https://news.ycombinator.com/item?id=43827342