36C3 - A systematic evaluation of OpenBSD's mitigations

media.ccc.de/v/36c3-10519-a_s...
OpenBSD markets itself as a secure operating system, but doesn't provide much evidences to back this claim. The goal of this talk is to evaluate how effective OpenBSD's security mitigation are, in a systematic, rational and comprehensive way.
OpenBSD's website advertises a secure and modern operating system, with cool and modern mitigations. But no rational analysis is provided: are those mitigations effective? what are their impacts on performances, inspectability and complexity? against what are they supposed to defend? how easy are they to bypass? where they invented by OpenBSD or by others? is OpenBSD's reputation warranted?
This talk aims at answering all those questions, for all OpenBSD's mitigations, because, in the words of Ryan Mallon:
Threat modelling rule of thumb: if you don’t explain exactly what you are securing against and how you secure against it, the answers can be assumed to be: “bears” and “not very well”.
For example, OpenBSD added last year a MAP_STACK flag to its mmap function, and branded it as a security measure against "ROPchains". But this mitigation used to be part of Windows until 2012, and was removed because of at least generic public bypasses. It's also implemented on Linux since 2008, but for other reasons :)
All the research done for this talk is available on isopenbsdsecu.re
stein
fahrplan.events.ccc.de/congre...