36C3 - A systematic evaluation of OpenBSD's mitigations
media.ccc.de1 HN recommenders · 2020–2024
18K views · talk · dated · Uploaded 2019-12-29
A 36C3 talk that systematically evaluates OpenBSD's exploit mitigations, asking how effective they really are and what they cost in performance, complexity and inspectability. It challenges the project's security marketing.
Cited in OpenBSD threads as a skeptical, evidence-based counterpoint to claims about its security, though some dispute its objectivity.
47:18The Tragedy of systemd
linux.conf.au
51:32Behind the Scenes of iOS Security
Black Hat
12:01Why Electronic Voting Is Still A Bad Idea
Tom Scott
51:22USENIX Security '18-Q: Why Do Keynote Speakers Keep Suggesting That Improving Security Is Possible?
USENIX
42:50Defcon 18 Changing threats to privacy Moxie Marlinspike Part
killab66661
1:48:55The Thirty Million Line Problem
Molly Rocket
1:03:51VCF East: Ken Thompson interviewed by Brian Kernighan
Vintage Computer Federation
1:04:04LISA11 - Fork Yeah! The Rise and Development of illumos
USENIX
6 comments from Hacker News
Here's a recent talk evaluating OpenBSD's security mitigations: [VIDEO] The objectivity of it is up to debate though, some argue that it is biased/unfair.
Here is the presentation which provides more context than the slides alone: [VIDEO] I've watched it before and it is compelling; however, at the end of the day, an OS that tries to take security seriously is probably better than one that doesn't. The OpenBSD code is small and I suspect that the defects/KLOC is far less than other projects capable of routing. I'd love to hear more critiques for using it as a home router though.
Yeah he doesn't seem paranoid at all, just very aware of what holes the tech stack has. In fact, some people have argued that de Raadt (and the OpenBSD team) are not paranoid _enough_: [VIDEO] "36C3 - A systematic evaluation of OpenBSD's mitigations"
I use OpenBSD as a daily driver. To make GP's point though, there are a few video's [0] and blog posts dissing OpenBSDs security claims. [0] [VIDEO]
Indeed, in CCC's "systematic evaluation of OpenBSD's mitigations"[0] the presenter explicitly calls out OpenBSD's tendency to present mitigations without specific examples of CVEs it defeats or exploit techniques the mitigations are known to defend against: > Proper mitigations I think stem from proper design and threat modeling. Strong, reality-based statements like "this kills these vulnerabilities," or "this kills this CVE; it delays production of an exploit by one week." And also thorough testing by seasoned exploit writers. Anything else is relying on pure luck, superstition, and wishful thinking. Some of OpenBSD's mitigations are excellent and robust in defensiveness; others are amorphous and not particularly useful. [0]: [VIDEO]
I wouldn't say it's missing. I deliberately generalized. I mentioned RBAC as an example. If people want to learn more there is no shortage of info. There was even a talk[0] at the 36th CCC. [0] - [VIDEO]