"Threats"
summary
Argues that the real risk is account theft and mass surveillance, not abstract threats, and that engineers can fix much of it now: stop letting build systems and dependency hell eat development time, deploy HTTPS everywhere, and add end-to-end encryption using libraries rather than inventing crypto — cites working projects like open keychain, recommends learning RFC 4880 and using existing OpenPGP implementations in Go, Ruby, Python or Node.js, and get legal to sign off on threat models.
AI-written summary · about
chapters (5)
- 0:00Introduction and industry
- 1:34The issue of yak shaving
- 3:14Security as a priority
- 5:07The importance of privacy
- 6:31Call to action for security
related talks
18mKeynote
57mMaking Security Priority Zero
40mSecurity today and tomorrow : Adapting the rules to suit technological advances
51mThinking Differently About Security
01h 06mKeynote: Devaluing Attack: Disincentivizing Threats Against The Next Billion Devices
41mSecurity: The world is broken and you are guilty
18mDesigning for Security Outcomes
42mKeynote: How much security is too much?