2 ms·
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/s
by edent 7y ago
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-and-verifying-an-https-request https://security.stackexchange.com/questions/193559/saving-a...
- jayd16 7y agoLooks 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.