Month 8 Reading

Primary sources, and they matter more this month than any other. Cryptography is the domain where secondary summaries (and AI paraphrases) are most often subtly wrong. It is also where the authoritative documents (the RFCs, the NIST publications) are unusually readable. Read the RFC, not the blog about the RFC. When this month’s reading and an AI explanation disagree, the reading wins, every time.

Core (read these)

Reference (consult as needed)

On AI use this month

  • required AI-ETHICS.md at the repo root. Re-read it before your first lab. Decision-tree question Q2 (“could the AI’s output be wrong in a way you would not catch?”) is the entire month’s AI discipline in one line.
  • required SAFETY.md at the repo root, specifically the section on legal targets: CryptoHack and your own machine are in scope; nothing else is.

A note on sources, and on AI in crypto

This reading list leans hard on RFCs and NIST publications because they are the only sources that do not hallucinate. When you ask AI to explain a crypto concept in plain language (the one use this month allows), treat every factual claim it makes as a guess to confirm against the documents above. AI will tell you, with total confidence, that one TLS message comes before another when it does not, that a mode of operation provides a property it does not, or that a key size is safe when the standard says otherwise. The reading list is your defense. The verification ritual is the test of whether you used it. In this field, “I read it in the RFC” is the only sentence that ends an argument.