You are signed in. Close

You are signed out. Close

Thank you. Your subscription has started. Close

Thank you. You will get an email when a new comic comes out. Close

We could not confirm your payment. If you paid, use the link "Sign in" at the bottom of the page. Close

Something went wrong on our side. Please try again in a moment. Close

Previous episode Domain validation: why a scam website can show the HTTPS padlock too

What the HTTPS padlock means: how your browser talks in secret on a Wi-Fi anyone can read

The TLS handshake: how HTTPS sets up a secret connection in one round trip

Before your browser sends a single word over HTTPS, it must agree on a key with the website. It must also check who is on the other end. The TLS handshake does all of this in one trip there and back.

  1. 1 Miva is back on the real café Wi-Fi. Her phone starts with a hello, and the hello already carries its mix. It doesn't wait for the shop to ask.Miva's phonehelloits mixshop.example

    Miva is back on the real café Wi-Fi. Her phone starts with a hello, and the hello already carries its mix. It doesn't wait for the shop to ask.

  2. 2 The shop answers in one go: its own mix, then, already scrambled with the new key it built from the two mixes, its certificate, its signature and a last word, "finished".shop.exampleits mixhellok%7#x!Qz&2shop.examplesignaturefinished

    The shop answers in one go: its own mix, then, already scrambled with the new key it built from the two mixes, its certificate, its signature and a last word, "finished".

The rest of this episode is for subscribers

Subscribe to read every premium episode. You can cancel when you want.

Paid yearly: $99 instead of $119.88

Next episode Forward secrecy: why a key stolen tomorrow cannot open what was recorded today

Share this comic

More comics