The SSL handshake is the short exchange your browser and a server run before an HTTPS page loads. By the end, the server has proved who it is and both sides hold the same secret key.
In modern TLS, neither side sends that key across the network: each one works it out for itself.
SSL or TLS?
SSL was the original protocol, from the 1990s. Every version of it is now considered insecure and switched off in modern browsers. Its successor is TLS (Transport Layer Security). People still say 'SSL handshake' and 'SSL certificate' out of habit, but what your browser runs today is TLS, usually version 1.2 or 1.3.
What the handshake has to do
- Agree the settings: which TLS version and which cipher suite (the set of algorithms) to use.
- Prove the server's identity, using its certificate.
- Agree a shared session key that neither side ever sends over the wire.
The handshake, step by step
Here is a TLS 1.3 handshake, from the first hello to the first encrypted request:
A TLS 1.3 handshake between a browser and a server
Step 1 of 8: The browser says hello: the TLS versions and cipher suites it supports, plus its half of a key exchange.
Wondering how this was made? How we make these