OpenBSD 3.2 Available

fredrikv writes "Right on time, the files defining OpenBSD 3.2 have moved away from "snapshots" to the 3.2 directory of the OpenBSD mirrors. It is well known as the world's most secure operating system and now sports chroot'd Apache, fewer suid binaries, cool pictures for xdm-logins, a brilliant "antispoof" packet filtering rule and as usual includes lots of small updates and fixes. The files are there. What are you waiting for?"

Comments

*BSD

[moorg]

I thought the most secure OS was Windows 95. With NIC support like that nobody should be able to connect to your computer. On a more serious note, is OpenBSD recommended as an internet server over all of the other distros?

Threading issues resolved?

[Jack Wagner]

Does anyone know if they have the threading issues resolved with the kernel scheduler yet?

Tha last time I worked on any BSD code they were still having some low level race conditions occuring where the kernel scheduler would actually hit two proccesses at the same time which made it look like the program had some mutex corruption when it was actually a problem with the kernel and the semaphores they use to map memory for threads.

Granted if you're only using it as a workstation you'll never see it happen as it only happened under load but I found my clients were forced to move to a commercial Unix (I still recommend Sun) as they were the only products on the market able to handle enterprise type server loads with non-trivial applications. (okay, wer're talking n-tier Olog(n) cluster nodes which is very demanding but still...)

Warmest regards,
--Jack

Re:I'm waiting

[Geekboy(Wizard)]

Why? So it runs slower and is less secure?

what happened?

[tps12]

Wow, OpenBSD 3.2. For a while there I wasn't sure they'd ever get another release out (heh, and I'm not one of those "BSD is dying!" trolls, either!). It's always been one of my favorite BSD distros, and I'd never have switched to Linux if OpenBSD had had an SB Live! driver back in the day. The name "OpenBSD" was synonymous with "rock hard security."

It was sad to see the record for "no remote holes" disappear earlier this year. Even sadder when the holes in OpenSSH and -SSL were found. It seemed like the OpenBSD developers had maybe started to get lazy, or were too busy rushing to support the latest gee-whiz hardware and flashy features to keep an eye on security. And for most unix admins out there, flashy features aren't worth much if you don't have security.

I guess it's good to see that Theo isn't giving up. But I'm wondering if this release is going to be just another stepping stone on OpenBSD's recent path to shame, or if they are turning it around in an attempt to regain the glory of, say, 2.7. What do people think, is OpenBSD rising from the ashes or gasping its last breath?