Privacy & Security, Policy & Technology
summary
Claim: privacy is now a business and engineering requirement after Snowden, and practical tools exist to raise the bar quickly. Recommendations and specifics: stop using SHA‑1 (attacks cost ~$2–4M on EC2; browsers will flag it), prefer TLS everywhere, prefer Google Authenticator over SMS, consider U2F/YubiKey (~$50) for strong 2FA, and use certificate pinning or restricted CA lists to limit CA failures. Key discovery is solved with keybase.io proof‑based directory. Demoed usable end‑to‑end tooling: OpenPGP stacks (GPG, RFC4880), Java uses BouncyCastle (messy), and an OpenKeychain Android demo that imports keys and decrypts via device NFC works.
AI-written summary · about
chapters (31)
- 0:00Intro
- 1:06Software Developers
- 1:58Mr Snowden
- 3:32Criminals
- 4:20Misguided
- 5:16Not useful
- 7:23Tribal Culture
- 9:19The Gift of Civilization
- 10:21The Internet Engineering Task Force
- 12:45What is privacy
- 14:55Use HTTPS
- 16:36Failure modes
- 18:34HTTPS is flawed
- 19:20The Great Disguise
- 19:47The Mossad
- 20:33Economics
- 23:15Pinned certs
- 26:00Twofactor authentication
- 27:24Google Authenticator
- 28:48Fido
- 34:55Endtoend
- 35:58OpenPGP
- 36:32Public Key Private Key
- 38:46Public Keys
- 39:18Privacy Guardian
- 40:28Open PGP
- 40:46Go
- 41:06Bouncy Castle
- 44:57Keybase
- 46:55Open Keychain
- 47:14Cryptography on Android
related talks
45mRedefining Security: From Passwords to Biometrics and Digital Signatures
43mReflecting on Twenty Years of Usable Privacy and Security
16mSecurity, Fraud, and Compliance
44mPractical Security
47mPasswordless Web
32mPasswords are so 1990
01h 11mCrypto wars reloaded? Privacy technologies, cybersecurity ...
29mSecurity by(e) Design?