Use Cryptography; Don't Learn It
summary
Experience as a crypto-library maintainer shows concrete rules: prefer Themis: two-line GCM encryption or libsodium/NaCl for ready primitives rather than copying OpenSSL from Stack Overflow; watch out that CBC default in CommonCrypto causes subtle vulnerabilities; Android builds require manual BoringSSL compilation per architecture; HSMs give strongest key isolation but cost and vendor lock are real. Key management (derivation, rotation, storage) is the frequent failure point. Start with box solutions, then crypto systems, then libraries only if necessary.
AI-written summary · about
chapters (9)
- 0:00Introduction to cryptography
- 2:06Defining the data scope
- 6:06Choosing cryptographic tools
- 8:05Key management challenges
- 10:25The concept of boring crypto
- 15:43Hardware vs software security
- 21:03Cryptographic libraries
- 28:51Box solutions and tools
- 31:07Summary and best practices
related talks
40m 10 Things you Need to Know before Implementing Cryptography
47mPractical Security Foundations
52mTales from the Crypt: A Cryptography Primer
51mDon’t Throw Away the Key: What Developers Should Know about Encryption
55mCrypto for Developers: Making Sane Choices
28mModern Cryptography
01h 04m Cryptography For Newcomers - The hitchhiker's guide to cipher in devs 
32mForay into modern symmetric crypto