News for hackers. Stuff that matters.
Re:"OpenSSL has exploit mitigation countermeasures to make s... by jameshart on Wednesday April 09, 2014 @09:49AM (#7559224)
There are certainly large commercial entities who have sufficient incentive to keep OpenSSL secure that they really ought to be contributing actively to the project; I wonder whether Amazon might step up given how badly (and publicly - witness Mojang's taking minecraft services offline and pointing the finger at Amazon as the vendor they were waiting on to fix things - https://twitter.com/notch/status/453529143121309696) they got bitten by this vulnerability. Cloud hosting companies clearly have a responsibility to deliver trustworthy services, and that means they need to be deploying software stacks they can rely on not to screw them; either they will need to step up and support OpenSSL or switch to different SSL solutions that have stronger guarantees. Network appliance vendors like F5 and Cisco also have a clear interest in fixing this stuff. Question is, will they?

(disclosure - I work for IBM, though not in cloud infrastructure. What I say for Amazon applies to our cloud services guys too.)

Re:"OpenSSL has exploit mitigation countermeasures to make s... by ak217 on Wednesday April 09, 2014 @10:43AM (#7559562)
I'm not sure that OpenSSL is the project they ought to be contributing to. It looks to be beyond repair architecturally (as a project as well as codebase).
Re:"OpenSSL has exploit mitigation countermeasures to make s... by mikevm on Wednesday April 09, 2014 @10:49AM (#7559599)
How in the heck is this mess of a project so popular?
Re:"OpenSSL has exploit mitigation countermeasures to make s... by delinka on Wednesday April 09, 2014 @11:32AM (#7559905)
It's a readily-available collection of complicated things (ciphers, digests, cryptographic protocols, etc) that everyone needs. Implementing 'yourself' (your company, whomever) takes lots of time and thus money. It seems the world made the assumption that this open source project was the end-all be-all of cryptographic implementations.
Re:"OpenSSL has exploit mitigation countermeasures to make s... by niels_olson on Wednesday April 09, 2014 @02:10PM (#7561086)
This. How often are we told not to implement crypto ourselves? And the name is marketing perfection: OpenSSL. Yes, that's exactly what I want.
Re:"OpenSSL has exploit mitigation countermeasures to make s... by lern_too_spel on Wednesday April 09, 2014 @12:53PM (#7560531)
It was developed outside the US at a time when the US had export restrictions on strong crypto. Now that those restrictions are gone, anybody can just use NSS instead.
Re:"OpenSSL has exploit mitigation countermeasures to make s... by aaronblohowiak on Wednesday April 09, 2014 @11:19AM (#7559801)
Age, momentum; "network effects."
Re:"OpenSSL has exploit mitigation countermeasures to make s... by laumars on Wednesday April 09, 2014 @01:13PM (#7560671)
Are the alternatives much better? GnuTLS has had it's fair share of embarrassing bugs too and I can't think of a 3rd open source product that's as mature.
Re:"OpenSSL has exploit mitigation countermeasures to make s... by niels_olson on Wednesday April 09, 2014 @03:21PM (#7561661)
> a 3rd open source product that's as mature.

NSS, which is used by Mozilla and Chrome. For Apache, just google mod_nss or read this: https://stomp.colorado.edu/blog/blog/2010/06/04/on-setting-u...

It looks like NSS isn't supported on nginx. Hope somebody puts that on their todo list!

Re:"OpenSSL has exploit mitigation countermeasures to make s... by danudey on Wednesday April 09, 2014 @05:09PM (#7562413)
NSS is more complicated, for a lot of reasons. As I recall, it handles its own keystore which it doesn't share with other implementations (e.g. the ca-certificates package in Ubuntu/Debian); it requires you to initialize the keystore manually and teardown when you're done, but sometimes you don't know if anything else has done the initialization, so you don't know if it's safe for you to tear it down.

There are other issues as well; not blocking problems necessarily, but reasons why it might not be a great implementation or why it would break the way current SSL works for distro maintainers and users.