News for hackers. Stuff that matters.
Re:Forthcoming OpenSSL releases by ajsdlfsafas on Thursday February 25, 2016 @01:53PM (#11176738)
Re:Forthcoming OpenSSL releases by rkeene2 on Thursday February 25, 2016 @02:45PM (#11177206)
LibreSSL can't be used everywhere OpenSSL is currently used. Notably (and intentionally) missing is FIPS 140-2 support, which most (almost all?) commercial product that uses OpenSSL will rely upon for selling a FIPS 140-2 compliant or validated product.

Personally, I find Network Security Services (NSS) much better designed than OpenSSL/LibreSSL and wish more things would use it. Notably better is the use of an actual database to store objects. This really helps when you are using certificate revocation lists (CRLs) which may be huge blobs that change frequently.

Re:Forthcoming OpenSSL releases by X-Istence on Thursday February 25, 2016 @03:59PM (#11177736)
Wasn't there recently an announcement that OpenSSL was planning on removing FIPS 140 support in the near future and possible add it back at a later point in time?

Specifically mentioned here, OpenSSL 1.1.x won't have FIPS support: https://groups.google.com/forum/#!searchin/mailing.openssl.d...

Re:Forthcoming OpenSSL releases by rkeene2 on Wednesday March 02, 2016 @12:17PM (#11211315)
OpenSSL 1.0.x will likely remain supported (by someone, perhaps if not OpenSSL) for a long time due to this decision.
Re:Forthcoming OpenSSL releases by jamieb007 on Thursday February 25, 2016 @02:57PM (#11177307)
in some case, if you're able to switch libraries, you might also be able to switch languages and therefore skip on future issues inherent to C. Consider for example: https://golang.org/pkg/crypto/tls/
Re:Forthcoming OpenSSL releases by ck2 on Thursday February 25, 2016 @12:53PM (#11176211)
Glad they are fixing these but damn it is scary every time I see OpenSSL in a headline anymore.

btw

     HIGH Severity. 
     This includes issues that are of a lower risk than critical, 
     perhaps due to affecting less common configurations,
     or which are less likely to be exploitable. 
     These issues will be kept private and will trigger 
     a new release of all supported versions.
Re:Forthcoming OpenSSL releases by creshal on Thursday February 25, 2016 @09:12AM (#11174475)
And we just finished rebooting everything for glibc…
Re:Forthcoming OpenSSL releases by ams6110 on Thursday February 25, 2016 @09:30AM (#11174601)
I wonder what kind of new internet will emerge from the ashes of everything we've been using since the 1970s, when it finally all goes up in flames in the next few years.
Re:Forthcoming OpenSSL releases by creshal on Thursday February 25, 2016 @09:52AM (#11174761)
I think you underestimate the sheer tenacity of crappy solutions.
Re:Forthcoming OpenSSL releases by maaku on Thursday February 25, 2016 @11:47AM (#11175650)
I think you underestimate how badly things are failing.
Re:Forthcoming OpenSSL releases by creshal on Thursday February 25, 2016 @12:04PM (#11175811)
You'll need a really, really, really massive meltdown before people are willing to fork over the money necessary to restart from scratch. Not even nuclear meltdowns have historically convinced people to do that. Not even global warming is convincing people to do that.
Re:Forthcoming OpenSSL releases by ygjb on Thursday February 25, 2016 @05:30PM (#11178363)
Do tell, how badly are things failing?

Do you have data besides "look at all the vulns!"?

Do you have clear evidence of a negative economic trend that is linked to insecure software?

Re:Forthcoming OpenSSL releases by sbose78 on Thursday February 25, 2016 @01:28PM (#11176523)
Exactly what I was thinking.
Re:Forthcoming OpenSSL releases by krylon on Thursday February 25, 2016 @09:32AM (#11174617)
It's kind of unsettling to know there is a known vulnerability (at least known to some) out there and is going to stay unpatched for a couple of days. On the other hand, it is kind of nice to be able to brace for it mentally.

Does anybody know why the update is announced a couple of days in advance? Are e.g. maintainers of corresponding packages in Linux distros or *BSD given access to the code ahead of time so they can build new packages?

Re:Forthcoming OpenSSL releases by hannob on Thursday February 25, 2016 @09:46AM (#11174712)
>Does anybody know why the update is announced a couple of days in advance?

For server operators to be prepared. (And I would prefer if they would narrow the timescales more for that.)

>Are e.g. maintainers of corresponding packages in Linux distros or *BSD given access to the code ahead of time so they can build new packages?

Yes, but that doesn't require a public announcement.

Re:Forthcoming OpenSSL releases by krylon on Thursday February 25, 2016 @09:50AM (#11174745)
Thanks for clearing that up!
Re:Forthcoming OpenSSL releases by grantcox on Thursday February 25, 2016 @10:06AM (#11174860)
The early announcement allows our sysadmins to plan to work during those hours, and for the rest of our org to know that we'll have rolling infrastructure downtime, and that isn't the best time to plan a new feature launch etc.
Re:Forthcoming OpenSSL releases by riffraff on Thursday February 25, 2016 @09:52AM (#11174757)
presumably, the newly released code might teach malicious users what vulnerabilities are there, which in turn makes everyone who didn't patch quickly vulnerable.

By announcing in advance what is going to happen, people can be ready to update as soon as the patch is available.

Re:Forthcoming OpenSSL releases by noinsight on Thursday February 25, 2016 @09:17AM (#11174520)
Eager to see how this LibreSSL comparison chart will be updated: https://wiki.freebsd.org/LibreSSL#LibreSSL_.28and_OpenSSL.29...
Re:Forthcoming OpenSSL releases by CiPHPerCoder on Thursday February 25, 2016 @09:48AM (#11174729)
The "totals" seems a bit off...

16 + 7 = 19?

5 + 31 + 12 = 36?

Re:Forthcoming OpenSSL releases by krylon on Thursday February 25, 2016 @09:51AM (#11174753)
It is possible that some vulnerabilities affected both LibreSSL and OpenSSL. In those cases, the total would be smaller than the sum of its parts. However, that is just speculation on my part.
Re:Forthcoming OpenSSL releases by riffraff on Thursday February 25, 2016 @10:16AM (#11174927)
"total" in context is for a single project, the things beying summed are different levels of severity.
Re:Forthcoming OpenSSL releases by krylon on Thursday February 25, 2016 @12:02PM (#11175793)
Oh. In that case, I have no explanation to offer other than "math is hard", which does not sound very plausible in this case.
Re:Forthcoming OpenSSL releases by creshal on Thursday February 25, 2016 @09:54AM (#11174779)
The linked numbers on the Wikipedia article make more sense.
Re:Forthcoming OpenSSL releases by Mojah on Thursday February 25, 2016 @11:15AM (#11175373)
Mirror available here, in case the official site stops loading: https://marc.ttias.be/openssl-announce/2016-02/msg00001.php