liveBook · Manning

TLS handshake

As explained in Real-World Cryptography

A TLS protocol phase in which peers negotiate parameters, establish keying material, authenticate participants, and derive session keys.

The TLS handshake is the setup phase before protected transport. It helps client and server find compatible settings, exchange keying material, authenticate identities, and establish session keys. section 9.2.1

A handshake combines four jobs:

  • Negotiation selects a mutually supported protocol version and cryptographic algorithms. section 9.2.1
  • Key exchange establishes shared keying material between the peers. section 9.2.1
  • Authentication prevents a man-in-the-middle attacker from impersonating a peer, using certificate chains and browser trust. section 9.2.1
  • Session resumption can fast-track later secure connections without repeating the full key exchange. section 9.2.1

Checking a website identity

A browser can inspect a server certificate chain: a website leaf certificate links through intermediate certificates to a root CA trusted in the browser’s trust store.

How Real-World Cryptography covers it

How deep it goes
Explains the handshake’s major functions and certificate flow, while stopping short of complete message-level implementation detail.
Examples
Uses browser trust stores, Google’s certificate chain, and TLS 1.2 versus TLS 1.3 message ordering.
What it assumes
Assumes basic understanding of key exchanges and explains peer authentication through certificates and trusted certificate authorities.
What you can do after
Evaluate how peers negotiate parameters, establish keys, authenticate identities, and resume secure sessions.
How it connects
Connects negotiation, key exchange, authentication, session resumption, certificates, and web PKI.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Real-World Cryptography. The section links point to the parts of the book it draws on.