LightMySky
به انگلیسی

TLS: Putting the Pieces Together

A secure connection is assembled from all of it: a certificate proves the server's key, a key exchange produces a fresh shared secret, and a symmetric cipher with an integrity check carries the traffic. Reading the handshake in order is how the pieces stop being separate ideas.

No account needed. Progress saves in this browser.

What a learner can do afterwards

  • Order the steps of a handshake and say what each one establishes
  • Say which step fails when a certificate does not match the name asked for
  • Explain what forward secrecy protects and against what later event

1 · Read

A secure connection is built in order. First the client sends hello with an ephemeral key share, and the server answers with its own. Next the server proves its name with its certificate. Then a fast symmetric cipher with an integrity check carries the traffic. This is the full TLS1.3 handshake with ephemeral shares: no resumption, no early data. A key share is public; its matching private secret stays hidden and is deleted after use.

Try it together

You type bank dot example but the certificate says mail dot example. The browser stops at the name check. Key shares were already exchanged in hello, but without a passing check no authenticated application data flows.

121234567891011
A wrong computer clock misreads good dates. Certificates carry valid dates, so good sites fail on validity.

Forward secrecy comes from ephemeral key shares and erasing secrets after use. Each visit makes fresh shares, uses them, then deletes the ephemeral private secrets and session keys. If the long term signing key leaks later, past visits stay sealed because those secrets are gone.

After the secret is agreed, a fast symmetric cipher with an integrity check carries the traffic. Plain text would waste the secret, so the cipher guards every later message.

asked name: bankcertificate: mailnames differ, stop
The certificate binds the public key to the requested name. Bank against mail differs, so the name check fails first.

The key shares were exchanged in hello. Names get checked next at the certificate, and expiry belongs to certificates. A fresh shared secret is the only product here. The server also sends CertificateVerify, proving it holds the certificate private key, and both sides send Finished to confirm the keys before traffic flows.

Share hello and ephemeral key shares first, check the certificate next, then carry the traffic under a cipher that guards secrecy and integrity.

The rewritten reading was written for this dataset.

2 · Watch

به انگلیسی

Take it off screen

Print a worksheetA4 with an answer key page for grown-ups. No screen, no internet.

Where it sits

Then practise

8 questions wait behind this lesson, each with its answer explained. Every answer feeds the sky: stars light as they are learned, and dim when it is time to come back.

Spotted a problem on this page? Tell us
TLS: Putting the Pieces Together · Computing, ages 21 to 22 · LightMySky