Foundations — HTTPS — TLS handshake, certificates, CA

This page builds every word, symbol, and picture the parent note leans on, from absolute zero. Read it before the parent and nothing there will feel like magic.

1. Cleartext vs ciphertext — the two states of a message

Before any crypto, understand the two states a message can be in.

Look at the figure: the same envelope travels the wire twice. On top it is readable — the pickpocket in the middle just reads it. On the bottom it is shredded gibberish — the pickpocket copies it but learns nothing. Why the topic needs this: the whole point of TLS (Transport Layer Security) is to move the message from the top wire to the bottom wire. Every other concept exists to make that switch possible and safe.

2. A "key" and what encryption really is

Why the topic needs it: HTTPS scrambles bulk data with a shared key. Everything about the "handshake" is really the struggle to get both sides holding the same key without ever mailing that key across the open wire.

3. Symmetric vs asymmetric — one key or two?

This is the single most important fork. The parent calls it "hybrid crypto".

In the figure, the symmetric case (left) shows one identical key on both sides. The asymmetric case (right) shows a lock everyone can snap shut (public key) but only the owner's separate key (private key) can open. Why two directions matter:

• Anyone locks with your public key → only you open it → this delivers a secret to you.
• You lock with your private key → anyone opens it with your public key → this proves the box came from you (a signature — see §5).

Full detail lives in Symmetric vs Asymmetric Encryption.

4. Modular exponentiation — the mod and the gᵃ

The parent's Diffie–Hellman box writes $g^a\mathrm{mod}p$. Two symbols to earn: the exponent and mod.

Why the topic needs it: this is the mathematical engine of key exchange — see Diffie–Hellman Key Exchange. It lets two strangers agree on a secret in public because reversing $g^a\mathrm{mod}p$ (the discrete log problem) is believed too slow to compute — provided the parameters above are chosen well.

5. Hash and digital signature — fingerprints and seals

Trace the figure top to bottom: document → hash (fingerprint) → locked with the sender's private key = signature. On the right, the receiver unlocks with the public key and independently re-hashes; equal fingerprints = authentic.

Why the topic needs it: certificates are signed documents, and the handshake's "Finished" message is a signed/MAC'd fingerprint of the whole conversation — this is how tampering is caught. Depth in Digital Signatures & Hashing.

6. Nonce, MAC, and the transcript

7. Certificate, CA, and the chain of trust

Now the pieces assemble into identity.

The figure is a ladder: your browser stands on the root it trusts (bottom, pale yellow). Each rung above is signed by the rung below. If every signature checks out up to the leaf, you trust the leaf's public key.

Why the topic needs it: key exchange alone is useless if an attacker hands you their public key mid-wire (MITM). The certificate + chain proves the public key really belongs to the domain — and expiry + revocation stop stale or stolen certs from being reused. This is the world of Public Key Infrastructure (PKI).

8. The lower plumbing — TCP, DNS, HTTP

TLS does not run in a vacuum; it sits on top of existing layers.

Why the topic needs it: "HTTPS on port 443" means: DNS finds the server, TCP connects, TLS negotiates the tunnel, then HTTP flows safely. The parent's handshake is step 3 of that chain.

Prerequisite map (how the pieces feed the topic)

Read this list bottom-up: each idea rests on the ones named before it, and the last line is the topic itself.

• cleartext vs ciphertext → needs nothing; motivates everything.
• key + encrypt/decrypt → builds on cleartext/ciphertext.
• symmetric crypto and asymmetric crypto → both build on key + encrypt/decrypt.
• modular exponentiation $g^a\mathrm{mod}p$ → builds on asymmetric crypto → feeds Diffie–Hellman shared secret.
• hash + digital signature → builds on asymmetric crypto → feeds certificate + CA + chain.
• nonces + MAC + transcript → build on symmetric crypto.
• DNS + TCP + HTTP → the plumbing underneath.
• HTTPS / TLS handshake ← is fed by all four streams above: Diffie–Hellman (agree a secret), certificate chain (prove identity), nonces/MAC/transcript (freshness + integrity), and the DNS/TCP/HTTP plumbing.

Equipment checklist