11 ms·
What every IT person needs to know about OpenBSD (2021)
- nottoplan39231 3y ago> What every IT person needs to know about OpenBSD First thing that we need to know - what is it? I had to look up on Wikipedia for information on what this is and what it's trying to solve. So my takeaway is that not every IT person needs to know this since I've been in the field for over 20 years and worked at a wide range of tech companies (from Unicorns to academia to fortune 100 companies to FAANG or whatever the name is now)? It's a shame when articles like this make so many assumptions about their audience. It reminds me of the RTFM days of tech that was dismissive, arrogant, and not all that helpful.
- system2 3y agoIt is just a linux distro. Not a handsome one either. "Every" IT person needs to learn how to use Windows Server first before jumping onto these things because 90%+ companies are using Windows Server.
- the_only_law 3y ago> It is just a linux distro. No it’s a BSD.
- system2 3y agoLinux, Unix. For someone who is asking what it is, simpler response is "just a distro".
- timc3 3y agoExcept it really isn’t, distros usually refer to different distributions of Linux but not different types of operating system. I usually say to layman that they are different forks of unix from many years ago. OpenBSD and Linux have a lot of the same tools to be sure but they are different enough that you have to learn them both if you are administering them.
- lproven 3y agoYou are very badly wrong. You are also exposing your own severe ignorance. And you are exactly the sort of person who needs to read the article.
- system2 3y agoCalm down.
- skotobaza 3y agoDo you expect every article to assume that everyone reading it is ignorant of the topic? Then we would have same lines of introductory text in most articles which would be time-wasting since you can go and google the software that you don't know about.
- ilyt 3y ago[flagged]
- peter_d_sherman 3y ago>"All of those features have been integrated in the OpenBSD source tree, and with the developers admonished to adhere to the rule "where it is possible to spot damage, fail hard". -which means that poorly written software will crash a lot more often on OpenBSD than elsewhere." In other words, testing software on OpenBSD -- is one great way to find some types of bugs and other incorrect software designs... In other words, testing software on OpenBSD -- can be thought of as applying a higher degree of correctness, rigor, and discipline -- to Software Engineering... Sort of like a 'lint', but for a runtime... It's not the only software test, that's true, not by a long shot -- but testing on OpenBSD would make a valuable addition to any professional software test corpus... >"That in itself should make the platform attractive to developers." It is, and it does!
- uticus 3y ago> In a prime example of hacker humor of the time, a T-shirt featuring one of the early appearances of Puffy the blowfish that would become the project mascot touted the Blowfish password hashing algorithm which remains the default on OpenBSD both with the picture caption "So long and thanks for all the passwords" just below Puffy on the front, along with the full source code of the blowfish function on the back. Where do I get this t-shirt?
- 1vuio0pswjnm7 3y agoAccording to the Addendum NetBSD is older than FreeBSD.
- Sunspark 3y agoFrom the chronological perspective of a few months! Not even a year. FreeBSD has certainly received a lot more development hours compared to NetBSD. It would be interesting to read a write-up one day where all the BSDs say what they grew since their initial releases.
- NoZebra120vClip 3y agoThis appears to have been published in the second half of 2021. I recall some heady weeks in 1998, attempting to enable IPSEC between my twin OpenBSD Apollo 425t systems. "hard and near impossible to debug from an almost-working to a fully working setup" is an understatement! I never got it to the almost-working stage!
- jzb 3y agoI tinkered with OpenBSD a long time ago and found installing was more of a headache than I cared for - specifically disk partitioning was a chore. I wonder if that’s gotten much better? Can’t see myself switching to OpenBSD at this point, but I’d try it just for fun if the installation has improved enough.
- sgt 3y agoIt's like an filter to determine whether the user is worthy enough to use OpenBSD. Last time I used OpenBSD must have been back in 2000, 2001. Extremely well built system and the impact it has had on the world is mind blowing. I later changed to FreeBSD which had a bigger community and better support for graphics drivers, etc.
- detourdog 3y agoI think you might be right. The partitioning is very old school but if you need old school partition it's right there. If you don't need old school partition learn what you do need and move on. The documentation has always matched the experience with OpenBSD. I enjoy OpenBSD simply becuase I know where to find the documentation. Some OS's have so many variations that I'm overwhelmed. Considering the goals of OpenBSD the partitioning is a feature and structural.
- jmclnx 3y agoOne thing for people coming from Linux. If you decide to put everything in one large partition (not really recommended), always make sure /usr/local is on its own partition. If you do not do that, some ports will core dump. If you use one big partition, you will need to disable an important security feature to allow the ports to run.
- doublerabbit 3y ago> If you do not do that, some ports will core dump. What ports are you talking about? I'm using FreeBSD as my daily driver, never had a port core-dump due to this.
- prettyStandard 3y agoAre any of the developers asking to switch to Rust?
- prettyStandard 3y agoWow, down votes for a question. As a non rust developer, and non BSD user, but tangently aware of these things I am just trying to understand the energy of these communities. Guess I got my answer.
- inferiorhuman 3y agoOpenBSD is a tier 3 platform for Rust because of their release policy (frequent releases, no guaranteed backwards compatibility). Unless that changes it's unlikely that you'll see OpenBSD promoted beyond tier 3. From the OpenBSD side it's unlikely they'd adopt a language that's relegated them to the lowest priority.
- irdc 3y agoConsidering OpenBSD still supports some fairly old platforms[0] (for fairly good reasons, mainly that it helps catch bugs and keep the source tree portable) I don't see that happening soon. 0. https://www.openbsd.org/plat.html https://www.openbsd.org/plat.html
- inferiorhuman 3y agoAs an aside, github's issue search has really gone to shit. On that list, I think only the Loongson and Landisk architectures are in the not likely to ever be supported. The rest are all supported by LLVM and/or GCC with various efforts to support them in rust.
- 634636346 3y agoTheo isn't a "Code of Conduct" type of guy. Not a good fit. Though the license of the Rust compiler (MIT/Apache) does at least make it a possibility.
- deleted 3y ago[deleted]
- BaculumMeumEst 3y agoThere is nothing that every IT person _needs_ to know about OpenBSD. Most probably do not know it exists, and there is no consequence.
- rewmie 3y agoI agree. To underline the futility of this article, the factoid it leads with was how many years OpenBSD has been around. That bit of trivia is completely irrelevant and has no technical meaning or direct implication. No one ever asked during unscheduled downtime "quick, does anyone know how many years OpenBSD has been around for?"
- mmmrk 3y agoIt does carry meaning, see https://en.wikipedia.org/wiki/Lindy_effect https://en.wikipedia.org/wiki/Lindy_effect. It's not something to know during downtimes, but at the point in time where you decide which technology to use going forward. Contrast this with the lifetimes of popular Javascript frameworks.
- csydas 3y agomaturity of a project definitely matters; in larger businesses, the maturity of a product and how long it's had to "get past the teething stage" is very important, and for projects with public repos/issue trackers, you can get a nice feel for how the devs handle critical bugs going into it, or check if a major pain point for you has come up before and how they handled it. the article is a call to get you comfortable picking/using BSD, and from my point of view it's reasonable to advertise its maturity.
- paulnpace 3y agoI'm not a professional in any of this, but just from reading comments it appears that devs seem to prefer the latest, greatest, coolest thing while admins seem to prefer the oldest, robustest, boringest thing.
- 3y ago
- rs_rs_rs_rs_rs 3y agoThat obsd fanboys can't code mobile friendly sites.
- simondotau 3y agoI think if a web page formatted with nothing more than <h1>, <h2> and <p> tags isn't displayed well on your phone, the failing is with your browser, not the page. Surely a web page with utterly default style and zero layout should be a minimally cromulent experience on any device. It's just headings and paragraphs, with the occasional bullet point and indent. There's no stylesheet. There's no reference to millimetres, pixels or point sizes. Everything is defaults.
- accrual 3y agoAmazing that I would run into the owner/operator of Whirlpool on hn. I used the site a lot back in the day for modem/networking help. Thanks for all the fish!
- rs_rs_rs_rs_rs 3y agoThe website from your HN profile works fine on mobile. Why did you put in the work for that and not rely on the "defaults"?
- simondotau 3y agoIs that a serious question? I'll offer a serious answer if so, even though it's an absolute non sequitur.
- rs_rs_rs_rs_rs 3y agoIt is absolutely a serious question.
- simondotau 3y agoInformation density, feature density, and distinctiveness. Also it's fun.
- jmclnx 3y ago>which means that poorly written software will crash a lot more often on OpenBSD than elsewhere. And this is why I test everything I write for use at work on OpenBSD, it has helped me find some issues with items I have written for use on an application hosted on AIX
- o11c 3y agoA more significant issue, in my experience, is that a lot of useful nonstandard APIs simply do not exist on the BSDs, under any name - or worse, exist with unstable names, so you have to #ifdef your source code to make it work with more than one release. There is no equivalent to Linux's "we do not break userland". FreeBSD is generally assumed to be the least painful, but I usually don't even bother with that these days. If someone cares they can do the work.
- SoftTalker 3y agoYes, an OpenBSD release is a full system: kernel + userland. Running anything from a different release might work, but isn't supported and you won't get any help if something breaks as a result. Also there is no "LTS" release. The prior release gets updates until the next release drops. So you need to plan on release updates every 6 months. Luckily "sysupgrade" is usually painless but you need to check the release notes and packages you have installed for potential extra work (e.g. if you're running Postgres and it got a major version bump, you'll probably need to upgrade your database).
- accrual 3y agoSmall nit, but you get 12 months of support, not 6. > Patches for supported releases are also incorporated into the -stable branch, which is maintained for one year after release. https://www.openbsd.org/errata73.html https://www.openbsd.org/errata73.html
- detourdog 3y agoThe downside to OpenBSD to understand what you are using and monitor how to keep it going from release to release.
- peter_hansteen 3y agoFor those looking for nicer formatting, the article is also available as a three part APNIC guest blog post https://blog.apnic.net/2021/10/28/openbsd-part-1-how-it-all-started/ https://blog.apnic.net/2021/10/28/openbsd-part-1-how-it-all-... (links to the other two articles should be very easy to find from there) or the original blogspot version https://bsdly.blogspot.com/2021/09/what-every-it-person-needs-to-know.html https://bsdly.blogspot.com/2021/09/what-every-it-person-need... (and yes, the article was originally published in September 2021). The nxdomain.no version is tracker-free other than my rather short lived nginx log.
- gglitch 3y agoLooks great in reader mode too. Thanks for your attention to structure and formatting :)
- kristiandupont 3y agoI have never tried any *BSD systems. What are they best suited for? Dev environments? Servers?
- jamal-kumar 3y agoWith OpenBSD in particular I like it because from the default install it's got a built in web server [1] which can handle most use cases. I can pretty much just put it anywhere and trust in the secure defaults that it provides, throw my own software on that server, and then have a pretty good standard from OS level to my own software on how secure that's going to be. It doesn't change much [2]. Linux doesn't really offer that. Yeah it's got PACKAGES that offer web server solutions (apache, nginx, whatever else) but then I gotta maintain those. I find myself having to patch everything on my OpenBSD boxes way less if I stick to how it seems to be intended to be used - When all I've got to maintain are my own secure os installation + configuration, and my own software that I wrote myself, literally no packages, it's really cool. [1] https://man.openbsd.org/httpd.8 https://man.openbsd.org/httpd.8 [2] https://www.openbsd.org/errata73.html https://www.openbsd.org/errata73.html
- detourdog 3y agoThe documentation and the source code is all you need to do anything with an OpenBSD system. There is no need to track down anything the OpenBSD doesn't explicitly provide or document. Sometimes you have to think real simple.
- loeg 3y agoThey're best suited for people who had a good experience with a BSD in the 90s and are sentimental about that. Otherwise, there's really no reason to go with them over a Linux system.
- ceeam 3y agoHopefully HAMMER2 is ported to it soon. No hope for ZFS. Having old school UFS is a deal breaker, even though most Linux users still live with a comparably old Ext4, but once you get used to ZFS you don't want to go back. -- FreeBSD user
- anthk 3y agoHammer2 might be a bit intrusive in the FS subsystem. Less than ZFS, for sure, but is not a trivial task.
- tiffanyh 3y agoAgreed and someone is working on the port. Really hope this lands in -current. It was updated just last month (June). https://github.com/kusumi/openbsd_hammer2 https://github.com/kusumi/openbsd_hammer2
- ninkendo 3y agoI put OpenBSD on my router earlier this year to get in-kernel NAT64 support and to learn pf, among other things. I’m massively regretting that choice due to the UFS root filesystem. Power outage? Hope you weren’t planning on your internet coming back up without manual intervention. Get ready to plug that keyboard in and type “fsck” manually at boot, and press “y” a few dozen times while it asks you questions about what to do with corrupted inodes. I hope none of that data is important to the correct operation of the system! A filesystem lacking journaling support in 2023 is an absolute travesty given that the rest of the world has had this problem solved for 25 years or so.
- xo5vik 3y agoGet a random fact about OpenBSD https://why-openbsd.rocks/ https://why-openbsd.rocks/
- inparen 3y agoIs there something in OpenBSD, which I cannot do in other bsds/*nixes ? Or, I can do something significantly better than other oses ?
- owenmarshall 3y agoIs it better than sliced bread, no. But it does some things better than other systems. First, it feels small enough that I understand what’s going on while still providing valuable services out of the box - a web server, load balancer/proxy, etc. But more importantly the pieces all play together to make a unified system: the load balancer can do layer 3 by interacting with the system firewall, httpd works with the built in ACME client for TLS. All those pieces benefit from being part of the system as a whole, by having very consistent tooling and support - things are named very consistently and share flags across the system, and are backed by very high quality manpages. Simply put it’s not perfect, nor revolutionary, but it gets a lot of things right.
- bfrog 3y agoIt’s too bad certain games don’t use this idea of random load locations to avoid injections. Seems like most game hacks basically work by reading/manipulating certain memory offsets which contain useful data. Unless I misunderstand them.
- accrual 3y agoThat's how I used CheatEngine back in the day. You would probe the game's memory looking for a value you can control (like health, item count, etc.) then increment/decrement it in game until you reliably found which location in memory was changing. Then you'd save it with a name and enjoy your cheat.
- blibble 3y agothis works against exploits that need that offset pointer to to run any code at all but doesn't work against something the user is voluntarily injecting as the user is quite happy to run the offset pointer locating code
- deadletters 3y agoYou're right! Moreover that's sort of how all exploits work if you really zoom out.
- saagarjha 3y agoMost games already use this (not as a security feature, but because the OS applies ASLR to them).
- doingtheiroming 3y agoWorth noting that because the man pages are so good, GPT4 is a rather good OpenBSD sysadmin. If you get stuck on anything these days, you can ask it.
- godber 3y agoI used to use OpenBSD about a decade ago, I liked it quite a bit. I haven’t paid attention for over a decade though. Does anyone know how the maintainer base has evolved? I guess my main question is will OpenBSD survive Theo’s death?
- dang 3y agoRelated: What every IT person needs to know about OpenBSD Part 3: That packet filter - https://news.ycombinator.com/item?id=29290663 https://news.ycombinator.com/item?id=29290663 - Nov 2021 (48 comments) What every IT person needs to know about OpenBSD Part 3: That packet filter - https://news.ycombinator.com/item?id=29186042 https://news.ycombinator.com/item?id=29186042 - Nov 2021 (1 comment) What every IT person needs to know about OpenBSD - https://news.ycombinator.com/item?id=28709505 https://news.ycombinator.com/item?id=28709505 - Sept 2021 (12 comments)
- snvzz 3y agoI am most sad about libressl, which is highly compatible with openssl yet profoundly better. Portable version exists and the Linux world should have replaced openssl by now, but for unknown reasons this is yet to happen. I am hopeful someday one of the larger distributions such as Debian will have the courage to step forward.
- devmunchies 3y ago> profoundly better How? Better/newer algorithms? Faster? Cleaner code? Better APIs?
- jiggawatts 3y agoAfter Heartbleed, BSD developers forked OpenSSL and "cleansed" it. They removed ridiculous amounts of unmaintained legacy code, rewrote much of the rest, and tightened the security. The old code was littered with conditional compilation macros that made it virtually impossible to reason about or test. There are just too many forks in the tree of possible compile flags. The style of "make this code work against every possible standard library" is broken and results in insane spaghetti code. Instead, the BSD team rewrote OpenSSL in terms of a modern, complete C standard library. Then instead of making their LibreSSL cryptography code have conditional flags in it, they wrote shims for the standard library so that it would work on platforms where there are missing functions. This results in far cleaner code that can be reviewed and tested with much greater confidence. I dug up a couple of presentations by the LibreSSL team 9 years ago. It's full of "Wat!?" moments, such as discovering the OpenSSL has its own implementation of malloc & free! Why? Because on one platform they nobody uses any longer, those functions were "slow"! So now they have a custom-developed poorly maintained heap full of security issues. Worse still, that custom heap does not benefit from the security features of modern allocators or analysis tools like valgrind. Watch: https://www.youtube.com/watch?v=-4psTQ1sX7s https://www.youtube.com/watch?v=-4psTQ1sX7s I love the bullet point list of insanity they cut out: - Ebcdidc support - DOS support - MacOS Classic support (pre OS 10) - Win16 support - VM Support - Big-endian AMD64 support (!?) That last one is a story in and of itself...
- uwagar 3y agois openbsd good for graphics and sound work/programming?
- pseudostem 3y agoVulkan seems to be incomplete. Graphics drivers for Nvidia are a problem due to the project not accepting blobs, not signing NDAs. And today I had a problem installing matplotlib (ninja gave some error). AFAIK, tensorflow and/or python libs are a problem with *nix as well. On the good side, the system is VERY predictable.
- toast0 3y agoLatency sensitive? I'd guess you'd have some issues, because I've read that OpenBSD doesn't have syscalls to set cpu affinity for userspace threads/processes, which means you're subject to the kernel scheduler and might have tasks move in less than ideal ways.
- accrual 3y agoThere is a small sub dedicated to gaming on OpenBSD: https://old.reddit.com/r/openbsd_gaming/ https://old.reddit.com/r/openbsd_gaming/ Most recent post shows an older version of Minecraft running. And OpenBSD can be a perfectly usable general desktop OS with some configuration.
- timc3 3y agoNot that I have ever enabled graphics or sound on my OpenBSD boxes - but I would say it’s probably not my first, second or third choice of OS for this. But my recording studio would probably bore you as I just run macOS for both graphics and sound work.