What the Handshake Achieves
TLS protects traffic between a client and a server. Before any application data moves, the two sides run a handshake that agrees on cipher choices, derives a shared secret, and authenticates the server.
The modern TLS 1.3 handshake is fast and secure by default. It works like this:
- The client sends a ClientHello offering supported cipher suites and a fresh key share.
- The server replies with a ServerHello, its own key share, and its certificate.
- Both sides combine the two key shares with Diffie Hellman to derive the same secret without ever sending it.
- The client verifies the certificate chains to a trusted root and that it covers the requested hostname.
Why It Is Safe
The secret is derived, never transmitted, so an eavesdropper cannot recover it. Because each handshake uses fresh key shares, capturing one session does not expose past or future ones, a property called forward secrecy.
Key idea
The TLS handshake lets two parties derive a shared secret over Diffie Hellman and authenticate the server with a certificate, so traffic is both private and tied to a verified identity.