3 ms·

The perception of OpenBSD's usage was always low. OpenBSD was always about network infrastructure and simple, super solid servers. It's never something you writ

The perception of OpenBSD's usage was always low. OpenBSD was always about network infrastructure and simple, super solid servers. It's never something you write blog posts about because of fancy bleeding edge setups. The chance is high that your packets travel through several OpenBSD boxes while surfing the web. Also virtualization was never a topic for OpenBSD[0] - it is not a use case for such a system. [0] http://kerneltrap.org/OpenBSD/Virtualization_Security http://kerneltrap.org/OpenBSD/Virtualization_Security "x86 virtualization is about basically placing another nearly full kernel, full of new bugs, on top of a nasty x86 architecture which barely has correct page protection. Then running your operating system on the other side of this brand new pile of shit. You are absolutely deluded, if not stupid, if you think that a worldwide collection of software engineers who can't write operating systems or applications without security holes, can then turn around and suddenly write virtualization layers without security holes." -- Theo de Raadt

papsosouid 13y ago
It seems like you didn't read my post. The perception of openbsd usage was not low, that's the point. OpenBSD was virtually unheard of it when it forked from netbsd, but in the days of the ipf -> pf replacement, openbgpd being developed, etc there was tons of blog posts, mailing list traffic, etc about openbsd. Your link about virtualization is about people absurdly thinking that virtualization buys them security. He said nothing about virtualization being "not a use case for openbsd". You do know openbsd has explicitly added drivers to support running under virtualization right?