Internet Protocols · Cluster
TLS
Handshakes, certificates, and record protection.
- 01 The TLS Record Layer: Framing, Fragmentation, and Sequence Numbers How application bytes become protected records: the five-byte header, the 16 KiB fragment limit, implicit sequence numbers, and how the AEAD nonce is assembled.
- 02 The TLS 1.3 Handshake: What Each Flight Commits To The four-message exchange that produces keys: what ClientHello offers, what ServerHello selects, why the transcript hash is the spine, and when a retry costs an extra round trip.
- 03 Path Building and Validity Checking in X.509 Certificate Chains How a TLS peer turns a list of certificates into a trusted path: name chaining, basic constraints, validity windows, and why path building is search rather than parsing.
- 04 The TLS 1.3 Key Schedule: Extract, Expand, and Why Order Matters How HKDF turns one shared secret into six traffic secrets, what the transcript hash does at each stage, and why early secrets are derived before the peer is authenticated.
- 05 Session Resumption in TLS 1.3: Tickets, Binders, and 0-RTT Replay How a ticket becomes a pre-shared key, what the binder actually signs over, why early data cannot be made replay-proof, and what servers do about it.
- 06 AEAD Usage Limits and the KeyUpdate Handshake Why a TLS 1.3 key has a byte budget as well as a record budget, where the numbers come from, and what happens when a connection outlives its key.
- 07 Name Matching and Revocation: What the Certificate Does Not Tell You Subject alternative names, wildcard coverage, and the two revocation mechanisms, including why a stapled response and a fetched response answer different questions.
- 08 What TLS 1.3 Removed: Renegotiation, Compression, and Static RSA The features dropped between 1.2 and 1.3, the attacks that motivated each removal, and the compatibility cost that came with a smaller protocol.
- 09 Encrypted Client Hello and the Limits of Hiding a Hostname How the outer and inner ClientHello split works, what the ECHConfig commits the server to, and which parts of a connection remain visible after ECH.
- 10 Traffic Analysis Against TLS: Record Lengths, Timing, and Padding What ciphertext lengths reveal about plaintext, how padding is expressed in the record layer, and why uniform padding is not the same as hiding a request.