News for hackers. Stuff that matters.

A comment on Why SSL was renamed to TLS in late 90s (2014). Parent comment

Re:Why SSL was renamed to TLS in late 90s (2014) by mcpherrinm on Monday June 16, 2025 @08:35AM (#44288963)
No: while the handshake is unencrypted, it is authenticated. An attacker can’t modify it.

What an attacker can do is block handshakes with parameters they don’t like. Some clients would retry a new handshake with an older TLS version, because they’d take the silence to mean that the server has broken negotiation.

[ Parent | on HN ]
Re:Why SSL was renamed to TLS in late 90s (2014) by mcpherrinm on Monday June 16, 2025 @03:43PM (#44292762)
well, unless both client and server have sufficiently weak crypto enabled that an attacker can break it during the handshake.

Then you can MITM, force both sides to use the weak crypto, which can be broken, and you're in the middle. Also not really so relevant today.

[ Parent | on HN ]