News for hackers. Stuff that matters.
Re:OpenSSL Security Advisory by theCricketer on Thursday December 03, 2015 @02:59PM (#10672137)
Just curious (I'm a nobody in the security field to doubt anything): What is the process to vet the correctness of the description of the severity? I imagine these notices are pretty important so when they describe subjective things like how difficult and likely it is to take advantage of this loophole, is there a standard for how to assess such things?
Re:OpenSSL Security Advisory by 102030485868 on Thursday December 03, 2015 @04:50PM (#10672938)
The one the OpenSSL follows is documented here[0]. There's also the CVSS[1] which covers a broader scope.

[0]: https://www.openssl.org/policies/secpolicy.html

[1]: https://en.wikipedia.org/wiki/CVSS

Re:OpenSSL Security Advisory by peterle on Thursday December 03, 2015 @03:24PM (#10672316)
The "severity" is often not accurate. OpenSSL recently marked an issue as lowly severe, but in fact its severity was high.

Don't trust them. OpenSSL is bad, use LibreSSL instead. OpenSSL == NSA. For sure they know weaknesses and actively exploit them if required.

EDIT: I'm talking about this advisory: https://www.openssl.org/news/secadv/20150108.txt

Re:OpenSSL Security Advisory by danielhlockard on Thursday December 03, 2015 @03:28PM (#10672347)
I'm not saying you're wrong, I'm just saying LibreSSL isn't bug free either: https://en.wikipedia.org/wiki/LibreSSL#15_October_2015 buffer overflows and memory leaks aren't great.
Re:OpenSSL Security Advisory by peterle on Thursday December 03, 2015 @03:34PM (#10672395)
Didn't say that.

Just take a look at a "security comparison" between LibreSSL and OpenSSL: https://en.wikipedia.org/wiki/LibreSSL#Security_and_vulnerab...

Severity LibreSSL OpenSSL

High 0 5

Medium 15 28

Low 7 10

Total 22 43

LibreSSL has had no "high" vulnerabilities, whereas OpenSSL had 5. Decide for yourself which way to go.

EDIT: Sorry, can't format that table nicely here..

Re:OpenSSL Security Advisory by bch on Thursday December 03, 2015 @04:13PM (#10672673)
> The "severity" is often not accurate. OpenSSL recently marked an issue as lowly severe, but in fact its severity was high.

...

> LibreSSL has had no "high" vulnerabilities, whereas OpenSSL had 5. Decide for yourself which way to go.

I'm not defending or apologizing for OpenSSL (or any project), but your rationale isn't consistent, seemingly only trying to evoke an emotional response.

Since heartbleed, lots of new SSL implementations have sprung up (Libre, Boring, etc), and hard lights have shone on OpenSSL as well. The scrutiny and competition will come to be win for all consumers of SSL. It's not clear to me (as a consumer) that any project has a huge leg-up over another (though Libre's wholesale dump of a tremendous amount of legacy code sounds like a step in the right direction).

Do we even know this won't show up in other (Boring, Libre) implementations as well ?

Edit: formatting

Re:OpenSSL Security Advisory by neerdowell on Thursday December 03, 2015 @05:31PM (#10673224)
> I'm not defending or apologizing for OpenSSL (or any project), but your rationale isn't consistent, seemingly only trying to evoke an emotional response.

The GP is pointing out that LibreSSL has avoided the 5 vulnerabilities that OpenSSL marked sev:high since the fork. There isn't any inconsistency about that, it's a pure apples-with-apples comparison.

> It's not clear to me (as a consumer) that any project has a huge leg-up over another

LibreSSL has avoided almost half of the OpenSSL vulnerabilities found since the work. What more do you want?

Re:OpenSSL Security Advisory by peterwwillis on Thursday December 03, 2015 @05:09PM (#10673082)
Format tip: prefix a block of lines with two spaces (on each line) and a newline before and after the block to turn it into a fixed-width font, then format ASCII-style.