My code is being hacked!
summary
Shows why common choices break real systems by demonstrating concrete failures: ECB leaks identical blocks, reuse of IV or stream keys enables two‑time‑pad recovery, and CBC + padding oracle lets attackers recover plaintext. Covers RNG categories (TRNG, PRNG, CSPRNG) and why seeding matters, explains Google’s ChaCha20 vs AES decision for disk sectors, and details side channels—timing, cache (Spectre/Meltdown), power analysis and glitching—that leak keys or flip auth bits so that non‑constant‑time code or simple memcompares become exploitable.
AI-written summary · about
chapters (9)
- 0:00Introduction to security talk
- 1:51Circles of enlightenment in security
- 5:32Encryption modes and IV pitfalls
- 11:28Authentication and encryption order
- 15:26Random number generators in crypto
- 17:18Timing attacks on password checks
- 21:30Power analysis and glitching attacks
- 25:39Side channel attack tools
- 26:41Q&A on secure coding
