Keynote: Safety and Security: The Future of C and C++
summary
Becomes WG14 convenor and catalogs concrete failures and fixes: a common compiler optimization simplifies pointer+len checks into Len<0 and removes bounds checks, GCC’s diagnostic for that was added but strict-overflow=3 is broken and effectively deprecated in GCC 8, Annex L’s bounded undefined behaviors (C11 analyzability) is written but zero compiler implementers adopt it, Toyota publishes recommended compiler flags and audits, Microsoft’s 2018 CVE root‑cause breakdown guides priorities, and Android’s Rust code shows zero memory‑safety CVEs so far.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:31Safety and security matter
- 5:25Community reactions to criticism
- 8:17Ethics in software
- 11:28Buffer overflow checks
- 21:29Compiler diagnostics trade-offs
- 25:22Quantifying security threats
- 28:56Historical failures lessons
- 33:09Functional safety vs security
- 38:31Poka-yoke undefined behavior
- 42:44Adoption challenges
- 45:40Correctness vs security
- 47:05Government regulation
- 48:28Alternatives to C/C++
- 52:25Future of C/C++
- 57:00Conclusion Q&A
related talks
44mWhere are we on security features?
01h 35mSafety and Security for C++: Panel Discussion
01h 26mVulnerable C++
21mSecurity Features status update
01h 06mSecurity Beyond Memory Safety - Using Modern C++ to Avoid Vulnerabilities by Design
34mMaking C Less Dangerous
01h 26mA Path to Practically Safe C++
01h 30mDangerous Optimizations in C and C++ Programming Languages