Explore Go Cryptography (John Arundel)（Z-Library）

# Explore Go Cryptography — Reading Guide ## 【One-Line Pitch】 A hands-on, test-first journey through cryptography fundamentals, where you build a working cipher system in Go from scratch—perfect for Go programmers who want to understand encryption, authentication, and security without drowning in math. ## 【Book Arc】 - **Opening (~0%–15%)**: Introduces why cryptography matters, sets up the learning philosophy (build simple → attack → improve), and establishes the cast of characters (Alice, Bob, Eve, Mallory). The book promises a gradual climb from toy ciphers to modern algorithms like AES, SHA-256, and RSA. - **Early (~15%–33%)**: Covers the foundations—what codes and ciphers are, how they differ, and why the shift (Caesar) cipher is the perfect starting point. Includes setup instructions for a Go project and the first test-driven development cycle. - **Middle (~33%–52%)**: Implements the shift cipher in Go, byte by byte. Introduces the "spherical cow" problem-solving technique, test-first development, and the core `Encipher` function. This is where you write your first real cryptographic code and tests. - **Middle (~52%–70%)**: Expands into keys, keyspaces, and cracking. Covers multi-byte keys, crib-based attacks, password security, and the mathematics of key strength. Includes building command-line cracking tools and understanding why some keys are weak. - **Late (~70%–90%)**: Moves to block ciphers, cipher modes (CBC, GCM), padding, and the `cipher.Block` and `cipher.BlockMode` interfaces. Introduces enumeration, benchmarking, and the practical limits of brute-force cracking. - **Ending (~90%–100%)**: Covers entropy, information theory, hashing, authentication (HMAC), key exchange (Diffie-Hellman-Merkle), public-key cryptography (RSA), and a brief tour of AES internals. Ends with quantum computing and post-quantum cryptography. ## 【Key Takeaways】 - **Cryptography is learnable by building** (Early): The book's core method is to implement a toy cipher, attack it, and improve it—this builds intuition far better than abstract theory alone. - **Test-first development is essential for crypto code** (Middle): Writing tests before implementation catches subtle bugs that could make your cipher insecure. The book models this discipline throughout. - **Keyspace size determines practical security** (Middle): A key's strength comes from the number of possible keys an attacker must try. The book shows how to calculate keyspace and why longer keys matter. - **Cracking is a design tool, not just an attack** (Middle): By writing a cracker for your own cipher, you learn what makes ciphers weak—and how to design against those weaknesses. - **Block ciphers need modes and padding** (Late): Raw block encryption isn't enough; you need cipher modes (CBC, GCM) and padding schemes to handle arbitrary data securely. The book implements these from scratch. - **Entropy is the measure of unpredictability** (Late): Randomness and entropy are the foundation of secure key generation. The book connects information theory to practical key generation. - **Modern algorithms are built on simple principles** (Ending): AES, RSA, and Diffie-Hellman are complex in detail but follow the same fundamental patterns you've been building—confusion, diffusion, and one-way functions. - **Don't roll your own crypto for production** (Early): The book is explicit that its toy ciphers are for learning only. Real security requires battle-tested libraries and protocols. ## 【Reading Tips】 - **Do the challenges**: The book is structured around coding exercises. Set up the Go project as described and work through each challenge—this is where the real learning happens. - **Skim the math, focus on principles**: If equations look intimidating, don't worry. The author explicitly says you can understand the general principles without the math. Focus on the conceptual explanations and code. - **Deep-read the cracking chapters**: The sections on keyspace, cribs, and brute-force attacks are where you'll develop the most intuition about why cryptography works (or fails). - **Treat the final chapters as a survey**: AES internals and quantum cryptography are covered with more hand-waving and less detail. Read these for awareness, not implementation. - **Use the GitHub code**: The book references code available on GitHub. If you get stuck, look at the reference implementation—but try to solve each challenge yourself first. ## 【Coverage Limits】 This guide covers the book's structure and key concepts based on available excerpts. The later chapters on AES implementation details, quantum computing, and post-quantum cryptography are only briefly represented in the source material. ##