7 ms·
> The OpenSSL group do not tell the LibreSSL group about vulnerabilities that they are fixing in upcoming releases. > Why? Well, they just don't. That's the
by noir_lord 12y ago
> The OpenSSL group do not tell the LibreSSL group about vulnerabilities
that they are fixing in upcoming releases.
> Why? Well, they just don't. That's the whole story.
Then the story sucks, security of core components underlying the internet is bigger than any one group.
Respect for end users would indicate that a simple heads up of a high severity bug to someone on the LibreSSL team would be the way to go.
- detaro 12y agoWell, according to (also unsourced, so no clue what the "real" story is) comments on the sister submisson [1] it is because LibreSSL doesn't want to take part in the embargo on reported vulnerabilities. [1] https://news.ycombinator.com/item?id=9216815 https://news.ycombinator.com/item?id=9216815
- noir_lord 12y agoIn which case and assuming that is accurate then > Why? Well, they just don't. That's the whole story. Could have been > Why? Well, we'd have liked to but they don't embargo reported bugs and we do. Clearer for everyone. Assuming it's true.
- gpvos 12y agoWouldn't that be "they embargo reported bugs and we don't"? (Or at least, I suspect LibreSSL wants to keep to its own embargo schedule.)
- Bluerise 12y agoThat is true. OpenBSD/Theo refuses to take part in embargos, which means they don't get a heads up. Don't have a citation right now, but Theo said that publicly when Hardbleed or so happened.
- tedunangst 12y agoNot true.
- alecco 12y agoThat's because they patch within a couple of days and don't want their systems unpatched for long (30 to 60 days!) when there is a known issue out in the wild. The flaws tend to get leaked, the temptation is big because there are huge money incentives. I bet if the embargo were for 5 days they would reconsider. But good luck with that with members like Microsoft, Cisco, Oracle, which a terrible reputation of postponing things the maximum possible.
- SloopJon 12y ago> I bet if the embargo were for 5 days they would reconsider. Here's a page describing the list in question: http://oss-security.openwall.org/wiki/mailing-lists/distros http://oss-security.openwall.org/wiki/mailing-lists/distros Here's the embargo policy: > Please note that the maximum acceptable embargo period for issues disclosed to these lists is 14 to 19 days .... In fact, embargo periods shorter than 7 days are preferable.
- alecco 12y ago19 days is an eternity for a security-oriented OS aimed at critical infrastructure like firewalls and proxies.
- paulv 12y ago19 days is nothing compared to how long it has taken non-linux firewall and proxy vendors to patch things in the past.
- numbsafari 12y agoMakes you wonder why people buy those products.
- danudey 12y agoAnd a lot of those vendors just never do. And a lot of users never update anyway. There's no reason to keep my enterprise servers insecure because Johnny Linksys doesn't have a patch that he's never going to install anyway.
- raverbashing 12y agoYeah, but based on the work of the LibreSSL team http://opensslrampage.org/ http://opensslrampage.org/ I wouldn't use OpenSSL for anything else if possible
- themartorana 12y agoOpenBSD's scorched earth policy regarding OpenSSL is so anti-community it's ridiculous. OpenSSL served the entire internet for years. I'm happy that it's been forked - nice that could even happen at all - and some of the cruft responsible for the recent flood of exploits will be fixed/removed, but the hate just seems petty.
- wtbob 12y ago> OpenSSL served the entire internet for years. Well, it gave the entire Internet a false sense of security for years, at least. > …the hate just seems petty. Have you read some of the cruft that the LibreSSL guys removed? OpenSSL has been a horrid mess. Sometimes you gotta admit that a Yugo is a really, really, really bad car.
- rjaco31 12y agoFalse sense of security? They provided the best SSL stack for years, and for free. Everybody knew for long that OpenSSL was a mess, and the harsh reality is that no one wanted to take care of it beside the few (almost benevolent) OpenSSL developers. So now, the OpenBSD guys come in with their almighty attitude, while they knew about it for years and didn't bother to do anything about it before. No one wanted to do that job before Heartbleed, so yeah, it's really uncalled for to be that rude. We should all be grateful the OpenSSL team did what they did for so long.
- rurban 12y agoYou must been living on an island over the last years. "OpenSSL was the best SSL stack for years?" Best no, only fast. PolarSSL (now "mbed TLS") is the best, to the best definition of best. Still better than OpenSSL, which was known to be fast but insecure and poorly managed, are the stacks used the biggest clients: * NSS used by Chrome, Mozilla, et al * GnuTLS used by exim, GNOME, et al. I'm not at all grateful to the OpenSSL team for using horrible software practices and putting their clients into danger.
- rlpb 12y ago> > Why? Well, they just don't. That's the whole story. It's not the whole story. Here's the whole story: http://lwn.net/Articles/601958/ http://lwn.net/Articles/601958/ "As it turns out, de Raadt had been asked if he wanted to join the distros list back in early May." "[de Raadt:] So I'll decline."
- deleted 12y ago[deleted]
- alecco 12y agoWay to cherry pick of a cherry picking. Theo meant he has no time to join yet another mailing list where OpenSSL security issues are very likely way less an 1% of the messages. Also, it's a Linux mailing list and he maintains a BSD distro, not much in common. I remember back in 98 he said he processed about 2500 emails a day (using a custom set of emacs macros). "I'm more an email processing system than a developer, sigh" (paraphrasing) Why can't OpenSSL have an simple early warning list like most other major software packages. It's only adding one CC field.
- rlpb 12y agoIt would be nice if he'd said that, rather than "Well, they just don't." which completely misrepresents the situation. AFAIK, he has never requested such a thing, anyway. The only requests I see come from third party apologists, not from him. He just complains that they don't give him access, when in fact they offered him access. > Theo meant he has no time to join yet another mailing list where OpenSSL security issues are very likely way less an 1% of the messages. Is it really that hard to filter for /openssl/i/?
- deleted 12y ago[deleted]
- worklogin 12y agoIs it really that hard to have a vulnerabilities mailer for important stuff?
- bdg 12y agoTheo has a reputation for this attitude. He's not entirely unlike Linus in that he's brilliant and people don't want to deal with him.