36C3 - A systematic evaluation of OpenBSD's mitigations
36C3 - A systematic evaluation of OpenBSD's mitigations on HackerTube: recommended by 1 Hacker News commenter across 1 month, 2020–2024.
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.
What HN commenters said
6 Hacker News comments link this video. Each one links back to its thread.
jronMar 2021Recommends
Here is the presentation which provides more context than the slides alone: ▶ this 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.
in “FreeBSD Core Team Statement on FreeBSD Development Processes” · View on HN
DEADMINCEJun 2024Cites it
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] - ▶ this video
in “OpenBSD, the computer appliance maker's secret weapon” · View on HN
q3kMay 2020Cites it
Here's a recent talk evaluating OpenBSD's security mitigations: ▶ this video The objectivity of it is up to debate though, some argue that it is biased/unfair.
in “OpenBSD 6.7” · View on HN
vngzsDec 2023Critical
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]: ▶ this video
in “OpenBSD – pinning all system calls” · View on HN
pseudostemDec 2022Critical
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] ▶ this video
in “Ask HN: FOSS Projects Worth Donating To?” · View on HN
MonkeyClubOct 2022Critical
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_: ▶ this video "36C3 - A systematic evaluation of OpenBSD's mitigations"
in “For personal reasons, I do not browse the web from my computer. (2007)” · View on HN