News for hackers. Stuff that matters.
Re:Code rot and why I picked OpenBSD by Quequau on Sunday January 04, 2015 @04:22AM (#8833932)
I've used OpenBSD for years in my router. Something that has given me a bit of pause recently, is that with all the various espionage revelations coming out in the past 14-16 months, I had expected the OpenBSD crowd to be out in force talking up the operating system but they've been surprisingly subdued. Just makes me wonder...
Re:Code rot and why I picked OpenBSD by glass- on Sunday January 04, 2015 @06:24AM (#8834118)
> I had expected the OpenBSD crowd to be out in force talking up the operating system but they've been surprisingly subdued

The OpenBSD motto is "shut up and hack". Look at the work that is being done recently with libressl, openssh, the new httpd, signify, static PIE, xorg privilege separation etc. etc.

They're letting the code do the talking.

Re:Code rot and why I picked OpenBSD by Quequau on Sunday January 04, 2015 @10:04AM (#8834562)
I don't think that the OpenBSD crowd's response to the OpenSSH vulnerabilities are an example of some motto of "shut up and hack" at all. In fact, I find their response to demonstrate the difference in reactions that got my attention.

Heartbleed provoked substantial discussion as well as the LibreSSL project.

Re:Code rot and why I picked OpenBSD by yellowapple on Tuesday January 06, 2015 @01:19PM (#8846014)
If by "OpenSSH" you actually meant "OpenSSL" (I'm a seasoned sysadmin and I still get those mixed up in conversation, so don't worry), then yes, the crowd's response was certainly an example of "shut up and hack": the OpenBSD devs wrote libressl to replace it, cutting out as much of the insecure cruft as they physically could.
Re:Code rot and why I picked OpenBSD by tedunangst on Sunday January 04, 2015 @11:34AM (#8834879)
What OpenSSH vulnerabilities?
Re:Code rot and why I picked OpenBSD by wtetzner on Sunday January 04, 2015 @02:34PM (#8835506)
You mean the OpenSSL vulnerabilities?
Re:Code rot and why I picked OpenBSD by gaius on Sunday January 04, 2015 @04:30AM (#8833941)
Those who know don't talk and those who talk don't know.
Re:Code rot and why I picked OpenBSD by pferde on Sunday January 04, 2015 @10:50AM (#8834714)
Now, if we could only get the latter to shut up and listen, and the former to start talking. Wouldn't that be wonderful?
Re:Code rot and why I picked OpenBSD by jlgaddis on Sunday January 04, 2015 @09:11AM (#8834423)
You reminded me of "Allegations regarding OpenBSD IPSEC" [0] which, WRT the recent news of the NSA (attempting to) compromise encrypted VPNs, makes me wonder a bit (although I don't believe the allegations in the linked e-mail).

[0]: http://marc.info/?l=openbsd-tech&m=129236621626462

Re:Code rot and why I picked OpenBSD by Quequau on Sunday January 04, 2015 @10:29AM (#8834646)
Yeah, I remember that controversy.

As I recall those allegations prompted the OpenBSD to team do a full code audit of the IPSEC stack and, while they did find a few bugs, the conclusion was that there was no backdoor and that the bugs they found were not intentional. I think it's really hard to respond these sorts of allegations and I'm not sure we could honestly expect more than that.

I'm really not trying to insinuate that OpenBSD is compromised or untrustworthy. I guess I'm just musing that, even though I've used OpenBSD for ages & ages and I do try to keep up with things in the OpenBSD world, I just don't grok the OpenBSD community... and that makes me feel uneasy sometimes.

Re:Code rot and why I picked OpenBSD by jlgaddis on Sunday January 04, 2015 @01:17PM (#8835255)
Yes, sorry, I wasn't intending to make any accusations or insinuations either. I've been following the Snowden/NSA stuff pretty closely, however, and even after reading the recent revelations WRT VPNs, I had forgotten about this OpenBSD IPSec controversy until you reminded me.

(JFTR, I run OpenBSD in production, trust it greatly, and never believed the allegations of FBI/NSA/etc. "tampering".)