9 ms·
Wouldn't OpenBSD a better choice than either FreeBSD or HardenedBSD if security is a focus? It also has better wifi support and a much more modern PF firewall.
by koiwacandy 6y ago
Wouldn't OpenBSD a better choice than either FreeBSD or HardenedBSD if security is a focus? It also has better wifi support and a much more modern PF firewall. OpenBSD is really "the" router OS. It makes a lot more sense. (no pun intended)
- adamcstephens 6y agoPerhaps, but is different enough that it would be a significant migration cost.
- cmeacham98 6y agoOpenBSD security is overstated in my opinion (and the opinion of others[1]), and I have serious doubts it would be worth the work to migrate to unless FreeBSD is absolutely terrible. 1: https://isopenbsdsecu.re/quotes/ https://isopenbsdsecu.re/quotes/
- _joel 6y agoIntigued as to why you think it's overstated. It seems pretty robust to me. Those quotes are fairly snipey and there's quite a bit of history behind the people to bias their opinion.
- cmeacham98 6y agoThe website includes actual analysis on OpenBSD security as well. OpenBSD has this reputation of having some god-like security where it's leaps and bounds above every other OS. I believe its security is actually relatively similar to alternative OSs like linux, and perhaps even less as containerization seems to be getting really popular on linux right now which allows linux to somewhat catch up to what I consider to be one of the biggest advantages OpenBSD had (pledge). Most of the advocacy I see about OpenBSD security seems to be misleading and/or vague. OpenBSD's own website[1] proudly claims that OpenBSD has had "Only two remote holes in the default install, in a heck of a long time!". What is "a heck of a long time", and where's the info about any vulnerabilities other than an RCE in the default installation? 1: https://www.openbsd.org/ https://www.openbsd.org/
- nimish 6y agoThe "trick" is the default install bit. OpenBSD's default install is very limited. Since there's basically nothing enabled, the surface is limited. They still pop up every few years or so.
- asclepi 6y agoIIRC, "a heck of a long time" refers to the time elapsed since the initial release of OpenBSD in July 1996. Patches for vulnerabilities are listed per release on https://www.openbsd.org/errata.html https://www.openbsd.org/errata.html
- tialaramex 6y agoOne example that is in my wheelhouse was illustrative of the not-always-clever attitude of OpenBSD to security. If you need certificates from the Web PKI (for your SMTP server, or your IRC server, or any other TLS server, but most obviously your web server) you likely want to talk ACME to Let's Encrypt or another CA. The popular way to do this is Certbot, a program written in Python. Clearly that's a lot of dependencies and thus potential attack surface area so not ideal. A popular alternative is acme.sh which is Unix shell code. So this is potentially a far smaller attack surface but shell is hardly the most auditable or secure language by default... OpenBSD ships acme-client which is written in C. Now, acme-client uses lots of OpenBSD flavour tooling to improve on its security, components of acme-client are sandboxed off from themselves and the rest of the system using pledge() and so on such that components with access to your private keys are not also doing TCP/IP. On the surface then although it's written in an unsafe language this looks like a good trade and it exactly fits OpenBSD's approach. However, the thing about ACME is it's built out of existing standard components such as Certificate Signing Requests. So instead of attack surface in Python, or Bash, or C, and trying to mitigate it with local sandboxing, you can choose to hand the CSRs to a completely separate system and so to literally airgap your private keys and all the TLS server code from your ACME implementation if you want. You can use CSRs with Certbot, you can use CSRs with acme.sh, but, they aren't an option with OpenBSD's acme-client at all. acme-client is the Beast so that a US President can be driven somewhere very dangerous and most likely get out of there alive - but just using CSRs is having him just make a video call and never leave the safety of the Oval Office.
- Covzire 6y agoThey're like the raspberry pi's of OS's, great to tinker with and great to use if you have a use case that fits it. The main focus of OpenBSD's security seems to be a low attack surface and slower adoption of certain things. The network stack is still single-threaded for example. It's great for a home firewall but their philosophy is pretty paranoid and slow moving to the point where they're great for what they are but not very useful in any actual commercial data centers.
- tptacek 6y agoIt's interesting that OpenBSD's security reputation is such an article of faith that this comment is light-grey now. I get that it's not supremely substantive, but "OpenBSD's security is overrated" is not a controversial statement in the software security community. They built their reputation on the 1990s OpenBSD security audit, which was a real innovation, but one that every other mainstream operating system has since picked up. Linux probably gets substantially more audit attention now than OpenBSD does, and is quicker and more open to deploying kernel countermeasures. I'd probably trust a minimal Linux distro with a decent kernel configuration more than I trust OpenBSD. Later The comment I'm responding to isn't light grey anymore; the perils of flouting the guidelines and talking about downvotes! I wasn't objecting to the votes, though, just noting that the C.W. on HN seems different than in specialized security communities.
- staticassertion 6y ago> is not a controversial statement in the software security community. Funny how often this happens. Maybe we need to do a better job of conveying these sorts of things - happens all the time that the security community at large considers X or Y to be obvious and well known, and then you find that actually very large portions of the larger tech community don't know that at all.
- tptacek 6y agoI want to be careful not to be seen as speaking for that whole community; I'm just saying, if you were in a gathering of vulnerability researchers, and you said "OpenBSD's security reputation is really overrated", you'd get shrugs, not gasps.
- saagarjha 6y agoThe issue here is that there is seldom consensus in the software security community when it comes to opinions of certain projects. This is doubly so when the project makes some good choices, and some not-so-good choices, like OpenBSD does. For a similar discussion, ask your local security engineer what they think about WhatsApp or Signal.
- 6y ago
- dleslie 6y agoI've seen this before and my thoughts on it are simple: ok, so OpenBSD does some silly and archaic things, but where are the exploits? I keep hearing that the security community has doubts about OpenBSD, but I don't hear about those doubts being validated.
- anarazel 6y agoWell, that could also be related to openbsd barely being used...
- initplus 6y agoPublishing content relating to security can be seen as a kind of challenge. See the blogs of many security researchers for examples. I can't see why this same effect would not apply to OpenBSD to a certain extent.
- saagarjha 6y agoOh, it does. It’s just that it doesn’t apply to an extent necessary for someone to spend enough time on it.
- scaladev 6y agoWhere are the exploits for TempleOS? Come to think of it, where are the users, and where do most security researchers direct their attention to?
- dleslie 6y agoIf SerenityOS can be a target for exploits then surely OpenBSD can. https://devcraft.io/2021/02/11/serenityos-writing-a-full-chain-exploit.html https://devcraft.io/2021/02/11/serenityos-writing-a-full-cha...
- Google234 6y agoOpen bsd is targeted and does get CVEs though... the question is about the amount of attention compared to other platforms
- brobdingnagians 6y agoThat site doesn't make a very cogent point and likes quoting tweets of people without substance; just because you have credentials doesn't mean you don't have to make logical points. It does have some criticisms that can be taken account of, though some are obsolete, and they do show that lots of other OSes have security mitigations too (lots of which had them before OBSD), but it really does appear to be written by someone with an axe to grind. If you want the other side, [1][2][3] from the OpenBSD mailing list have some discussion. From my understanding, OpenBSD is partly a research OS and written by developers for developers. They want other OSes to grow and get better and adopt more security features; I don't get the feeling they are trying to compete with other OSes, but rather cooperate. If you like it great, if not, then you are free to go somewhere else. Linux appears to have a very competitive environment with a lot of toxic power games and the desire to prove that it is the One True OS. The BSDs thankfully have less of that; I use Linux, BSD, Windows, and Mac OSX. I like all of them for different reasons; I hope they all continue to improve. There is room enough for all. [1] https://marc.info/?l=openbsd-misc&m=158906273407900&w=2 https://marc.info/?l=openbsd-misc&m=158906273407900&w=2 [2] https://marc.info/?l=openbsd-misc&m=158897658715925&w=2 https://marc.info/?l=openbsd-misc&m=158897658715925&w=2 [3] https://marc.info/?l=openbsd-misc&m=158886904708799&w=2 https://marc.info/?l=openbsd-misc&m=158886904708799&w=2