Learn
The full module catalog
21 modules covering the cryptography behind every HTTPS connection, SSH session, and signed transaction: how it works, why it's trusted, and why it's the thing post-quantum cryptography replaces.
Your board is asking about the PQC migration. Before you can answer, you need to know what "classic" crypto your organisation actually depends on today.
Start with your first win: See what's actually at risk (10 min) →Full track: 5 modules · 80 min
Foundations
Before the math: what cryptography is actually trying to do, and the 2,500-year arms race between codemakers and codebreakers that got us here.
20 minEvery public-key algorithm in this catalog leans on the same idea: a calculation that's easy in one direction and effectively impossible to undo in the other.
22 minOne-way fingerprints for data, and the mechanism that proves a message is authentic and untampered — without encrypting anything.
26 minA cryptographic hash is too fast for passwords. KDFs deliberately slow things down — and not all of them do it the same way.
11 min128-bit AES, 2048-bit RSA, 256-bit ECC — these numbers aren't comparable at face value. Here's how to actually read them.
10 minEvery key, nonce, and IV in this catalog assumes truly unpredictable randomness. When that assumption breaks, everything built on top breaks with it.
10 minThe bridge module: why everything above is called "classical" cryptography, and exactly what a future quantum computer would do to it.
11 minSymmetric-key
The same key locks and unlocks the data. Fast, simple in concept, and everywhere — from disk encryption to the bulk of every TLS session.
26 minNot every symmetric cipher works in fixed blocks. ChaCha20 generates a keystream instead — and paired with Poly1305, it's AES-GCM's fastest rival.
10 minPublic-key
Two mathematically linked keys — one public, one private — solve the problem symmetric crypto can't: how do you share a secret with someone you've never met?
30 minTextbook RSA is deterministic and malleable. Padding schemes are what actually make RSA encryption and signing safe to use in the real world.
13 minThe same public-key guarantees as RSA, with dramatically smaller keys — because the underlying hard problem is different math entirely.
28 minProtocols
Two parties agree on a shared secret over a public channel, without ever transmitting the secret itself — the idea that started public-key cryptography.
24 minA certificate is just a signed statement binding a public key to an identity. Here's what's actually inside one, and how revocation works.
24 minJWTs put a signed claim in every request header. They're everywhere in modern APIs — and a few well-known implementation mistakes keep recurring.
20 minThe protocol behind every remote login and git push combines the same primitives as TLS, arranged slightly differently.
10 minEvery padlock icon runs a coordinated handshake combining key exchange, certificates, symmetric encryption, and integrity checks — in under a round trip.
16 minTLS protects data in transit to a server. The Signal Protocol's Double Ratchet goes further — encrypting so not even the server operator can read your messages.
13 minPractice
A cryptographic algorithm can be mathematically unbreakable and still leak its secret key through how long it takes to run.
11 minBitcoin and Ethereum don't invent new cryptography — they compose the same primitives in this catalog into a specific, tamper-evident structure.
12 minYou don't need a working quantum computer today to be at risk today. Anything encrypted now with RSA or ECC can simply be recorded and decrypted later.
9 min