4 ms·
For those who have heard of OpenBSD but have not used it, I strongly recommend trying it on your next server appliance. I have been using it on my servers for s
by wyager 12y ago
For those who have heard of OpenBSD but have not used it, I strongly recommend trying it on your next server appliance. I have been using it on my servers for some time now and I have been very happy. The entire OS seems to be of substantially higher quality than Linux.
- krasin 12y agoDoes OpenBSD have an analog of Docker?
- valarauca1 12y agoDocker originated from BSD Jails which basically give you Chroot on steroids. The synchronization likely won't 100% work, with cron script you maybe able to just do that with git.
- elehack 12y agoJails are a FreeBSD thing. OpenBSD doesn't have them so far as I know.
- doomrobo 12y agosysjail is available for OpenBSD. >It provides a similar function as FreeBSD's jail(8) utility while being significantly more flexible. The package provides jail(1), a drop-in replacement of FreeBSD's jail(8) http://sysjail.bsd.lv/ http://sysjail.bsd.lv/
- jude- 12y agosysjail is not safe for jail-like use. Sysjail'ed processes can do Bad Things by exploiting concurrency races in the syscall interception layer. Relevant paper: http://www.watson.org/~robert/2007woot/2007usenixwoot-exploitingconcurrency.pdf http://www.watson.org/~robert/2007woot/2007usenixwoot-exploi...
- valarauca1 12y agoThis paper is from 2007, is it still not fixed?
- jude- 12y agoIt's my understanding that it's not fixable without some help from the kernel. The fundamental problem is that a program can race ahead of a userspace syscall policy enforcement framework (i.e. sysjail) by trapping to the kernel directly. The authors identify several ways this can be exploited to gain privileged information or invoke syscalls the OS allows but the framework tries to prevent.
- valarauca1 12y agoDid some quick googling. Yes apperently as of 2009 it was unfixed. Seems the problem is with systrace over arching architecure OR how the kernel works with systrace. Learned something new today thanks :)
- eksith 12y agoAlso things are deceptively simple. There's of course the initial hiccup for new users since the setup is a tad esoteric, but once past that, using it is very straightforward. It's not quite "set it and forget it" for servers, but pretty close IMHO. There's an attitude among the developers of making it extremely difficult to run sub-par code on the OS, which makes the overall quality of most ported apps high, quite stable and (unpleasant)surprise-free.
- thaumaturgy 12y agoIt's very close to set-it-and-forget-it. A buddy of mine is an overworked (and underpaid) sysadmin for a small ISP, and commented the other day that the OpenBSD firewall that I built for them 7 years ago (!) is still humming along nicely, they're still using and tuning its rulesets, and it wasn't vulnerable to shellshock. (This isn't to say that not updating a firewall for 7 years is good practice, obviously. I shouldn't have to say that, but HN.)
- kylec 12y agoI'm looking to set up an OpenBSD server myself. Things are going quite well, but I'm not looking forward to the upgrade process (as an example, here's 5.4 -> 5.5 http://www.openbsd.org/faq/upgrade55.html http://www.openbsd.org/faq/upgrade55.html). How easy has it been for you to upgrade?
- adamrt 12y agoIts actually very easy to upgrade OpenBSD. There is lots of information on that page and you should read it all, but the actual process of the upgrade is quick.
- keithpeter 12y agoFollowing -current and updating within a release Would you recommend the patch by patch process or the full check out code and compile?
- splaff 12y agoSuccess recipe I use: 1. Install a release. 2. Subscribe to the security list. 3. Patch any issues that turn up and may affect you using the instructions in the patch. Rarely this requires a reboot. Don't patch anything you don't need to. 4. Upgrade release a couple of weeks after it is released (everyone else has found the bugs then ;-) 5. To manage ports, subscribe to the ports mailing list, create packages yourself from ports on another machine and install them and upgrade them yourself if there is an upgrade or security hole posted. Before you do anything though, test it on another host properly. YMMV with all updates on all platforms.
- jmhain 12y ago> The entire OS seems to be of substantially higher quality than Linux. That's a pretty bold statement. Care to elaborate?
- wyager 12y agoSure. Everything is more reliable. Not one crash yet. When I use Linux, I would have expected several by now. Everything works perfectly out of the box and has sane and safe defaults. Everything is more consistent. For example, the ifconfig/iwconfig/wpa_supplicant/etc. mish-mash on Linux is replaced with just ifconfig. All interactions with the OS are straightforward and standardized. The code is substantially better. Less macrotanium, better naming, more understandable. There is clearly more attention to (and more expertise about) security. This is, of course, what OpenBSD is (rightfully) known for.
- ealexhudson 12y agoI would expect to run Linux for many, many months doing pretty hard work before expecting a crash. I genuinely can't recall the last crash I had that wasn't hardware-related - probably an early ext3 issue?
- cbd1984 12y ago> Everything is more reliable. Not one crash yet. Also true with Linux, of course. > Everything works perfectly out of the box and has sane and safe defaults. Same with Linux, at least in the distros I use. > Everything is more consistent. For example, the ifconfig/iwconfig/wpa_supplicant/etc. mish-mash on Linux is replaced with just ifconfig. All interactions with the OS are straightforward and standardized. "My way or the highway", in other words. Use the Only OpenBSD Toolkit or get out? > The code is substantially better. Less macrotanium, better naming, more understandable. Readability is subjective. Macros aren't inherently bad. > There is clearly more attention to (and more expertise about) security. This is, of course, what OpenBSD is (rightfully) known for. At the expense of everything else, it seems, including hardware support.
- eksith 12y agoThis was posted on HN a little while ago. It gives some great insight into their process : http://www.openbsd.org/papers/dev-sw-hostile-env.html http://www.openbsd.org/papers/dev-sw-hostile-env.html Summary: Basically, the development process for OpenBSD is the same as stomach acid. To survive this environment is an exercise in code correctness. I.E. It's designed to break things that aren't up to par. The end result is a platform that doesn't sacrifice stability and security (the two often are two sides of the same coin) for the sake of compatibility.
- Nux 12y agoI appreciate the OS, but I wish it had a longer lifetime, as it is I can't really set it up on servers in a serious manner. It might be good on firewalls though where they don't expose a lot of services to the internet.
- splaff 12y agoThat's not really a major concern if you've used it at all. Their lifecycle is security oriented and you only get reliable security coverage if you keep something up to date. There's no point in sitting around living off backports and patches forever as all that does is create work. It's pretty easy to upgrade as well. With respect to application services, they can evolve independently to the base OS as well.
- Nux 12y agoI've toyed with it, not sure if that qualifies as "used". As a DC sysadmin I live off backports and patches (CentOS). 99% of our deployed OSes are all supported a long (to very long) time.
- splaff 12y agoI used to do that but having had certain duff kernels and SMB packages out of RH, they can go to hell. This one took out our SMB/CIFS implementation in CentOS 6.2 forcing us to grab some windows licenses in the end (which I will add has been damn reliable): https://bugzilla.redhat.com/show_bug.cgi?id=476442 https://bugzilla.redhat.com/show_bug.cgi?id=476442 Still broken in CentOS 6.5 and Centos 7.0. Many people have raised this issue (google it) and it's always "fixed next release". Patched and built my own kernel in the end but by then it was too late. No thanks. Had enough of crap like that.
- Nux 12y agoWell, I won't turn this into a thread to fix that problem, but have you tried these packages? http://enterprisesamba.com/ http://enterprisesamba.com/ Having said that, switching to OpenBSD is not as simple. It's not just some random web server with 2 sites on it; we're talking many, many servers with a great range of software running on them and so on. Some of this software will not even run on OpenBSD at all and so on. The problems are many. :) The big linux distros - buggy as they are - are here to stay. Also, some interesting "statistics" from $dayjob. Our DC workload (dedicated servers) is mostly web stuff; when I joined the company in 2009 there were a reasonable amount of FreeBSD servers around; that number is now 0 (or very close); my opinion is that it went "extinct" because of poor binary updates and package management as well as lack of long term support. CPanel stopping to support it was probably the last nail in the coffin. I'm seeing a similar thing with Debian, Ubuntu LTS took over that customer base. OpenBSD - from our pov - is facing the same issues. I'd love to see more BSDs deployed, but this will not happen unless the above points are addressed. Add to that the lack of "kickstart"-like functionality, as well.