Re:API responses should be signed
by jayd16 on Monday January 20, 2020 @02:48AM
(#22097141)
They can share the exact same encrypted bytes they received. Others can verify those bytes with the cert as normal. Or do I have it wrong, and the traffic is only signed with the user signature after the handshake?
[ Parent
| on HN ]
You have it wrong. I also thought that was the answer. See these responses to my question on StackExchange https://security.stackexchange.com/questions/193559/saving-a...
Looks like the message is encrypted with a key derived by both parties but this produces a symmetric encryption. The client then has the ability to spoof encrypted server communications.
Re:API responses should be signed
by tsimionescu on Monday January 20, 2020 @03:14AM
(#22097266)
SSL data is encrypted with a symmetric, per-session key. Only the initial handshake is done through asymmetric encryption, and only the initial handshake uses the global public/private key pair.