Crypto for Developers: Making Sane Choices
summary
Recommendation focuses on concrete choices and failures: use Argon2 for password hashing (PBKDF2 only as a minimum), prefer AES-256 (or Salsa20) with authenticated modes like GCM not ECB, prefer elliptic curves such as Curve25519 / X25519 or Ed448 and signatures like EdDSA, use libsodium for sane defaults, treat RNGs as make‑or‑break (8‑GPU cracking rigs and a PHP ransomware case show how weak RNGs and fast cracking destroy security), and plan for post‑quantum migration.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:32About me
- 3:20Questions
- 4:19What is Cryptography
- 5:07What Cryptography isnt
- 7:27Technology agnostic
- 8:28Realworld scenarios
- 9:57Collisions
- 12:39Password hashing
- 16:57Balancing server resources
- 18:24Password cracking
- 19:33Secret encryption
- 24:11Cipher modes
- 27:28Authentication
- 28:58Public Encryption
- 30:18RSA
- 36:49Hash Functions
- 41:23Signatures
- 42:22Algorithms
- 46:09Schedule
- 46:28Random Generator
- 49:48Exciting and Boring
- 50:38Quantum Computers
- 53:54Serious Cryptography
- 54:12Cryptography Engineering
related talks
46mCryptography For Beginners
28mModern Cryptography
51mDon’t Throw Away the Key: What Developers Should Know about Encryption
44mCryptography Pitfalls
47mPractical Security Foundations
52mTales from the Crypt: A Cryptography Primer
01h 04m Cryptography For Newcomers - The hitchhiker's guide to cipher in devs 
36mUse Cryptography; Don't Learn It