What your browser can teach you about software security
summary
Browsers execute arbitrary untrusted code yet concrete engineering choices make them safe: sandboxing isolates high‑privilege data from untrustworthy inputs and follows a rule of two for boundaries, C/C++ internals run in constrained processes, and a performance-driven rewrite that puts Rust in Firefox (Stylo) reduces memory-safety bugs and produces measurable drops in serious security vulnerabilities while improving layout speed. Tools like TLS, wasm and bug bounties are outcomes, not substitutes, for these architectural fixes.
AI-written summary · about
chapters (4)
- 0:00Horror story to breakthrough
- 3:38Security architecture boundaries
- 7:49Incentives for secure development
- 10:17Key lessons and path forward
related talks
42mThe Perilous Future of Browser Security
35mNow you can trust the browser
30mDon't Get Owned by Dependencies: How Firefox Uses Wasm to Protect Itself from Exploitable Libraries
39mFearless Security with Rust
39mTaking front-end security seriously
21mWeb Browsers: Om nom nom
19mWeb Platform Security
50mLinux Security and How Web Browser Sandboxes Really Work