Free, high-quality cryptography textbooks are rare. Most introductory material splits into two unsatisfying camps: cookbook-style guides that teach you which library function to call without explaining why, and graduate-level treatises that demand measure theory before page ten. Boaz Barak's An Intensive Introduction to Cryptography — the lecture notes from his Harvard course — sits in the genuinely useful middle.

Based on the URL and the title, this is the full online edition of Barak's textbook-in-progress, freely readable at intensecrypto.org. Barak is one of the more thoughtful expositors in theoretical CS, and his approach to cryptography reflects that: he treats crypto as a branch of computational complexity rather than a bag of tricks. The "intensive" in the title isn't marketing — it means the book derives security properties from first principles, with proofs.

What a technical reader is likely to find here:

• Definitional rigor. Most engineers know that AES is "secure" but couldn't precisely state what that means. Barak's notes walk through IND-CPA, IND-CCA, and the reduction-based proofs that connect them to hardness assumptions.
• Modern coverage. Beyond the symmetric/asymmetric basics, the course historically covers zero-knowledge proofs, fully homomorphic encryption, lattice-based crypto, and post-quantum constructions — the actual frontier, not just the textbook 1990s pipeline.
• Pseudorandomness as the unifying concept. Barak's framing — that almost all of cryptography reduces to constructing pseudorandom objects from minimal assumptions — is genuinely clarifying once it clicks.
• Free and maintained. No paywall, no DRM, no $120 hardback. The notes get revised as the field evolves.

For practitioners, the value isn't that you'll write your own AES (you shouldn't). It's that after working through material like this, you stop treating crypto primitives as magic. You can read a protocol spec, identify the security game it's playing, and notice when something is off — when a "nonce" is being reused, when a MAC is missing, when a construction is leaking through a side channel. That intuition is exactly what separates engineers who quietly ship subtly broken systems from those who don't.

At three points and zero comments, this is precisely the kind of submission HN tends to upvote enthusiastically when someone notices it — a free, high-signal educational resource from a credible author. It just landed at the wrong moment in the queue.