News for hackers. Stuff that matters.
Re:My Heart Bleeds for OpenSSL by tptacek on Tuesday April 08, 2014 @08:33PM (#7556993)
Everybody wants prior warning, but very early in the process you hit a point where secret notices create more harm than help.

The worst situation you can be in is where everyone knows something is going on, but only a small group of people know what it is. At that point, the incentives strongly favor the attackers, who will work quickly to join the in-crowd and exploit the window of time where they know how to exploit the flaw, and site operators don't know enough about it to take it seriously.

It's especially hard to stage-manage these updates with open source software. Look at the patch; to someone who takes exploit code seriously, the vulnerability is instantly obvious. How was anyone supposed to give you a heads up without tipping off attackers?

Re:My Heart Bleeds for OpenSSL by chomp on Tuesday April 08, 2014 @09:00PM (#7557099)
I think we can agree that there is a happy medium between the slow and risky process of notifying every single organization, and only one SSL terminator "in the know".

The logistics of disclosure for something as ground breaking as this are probably very difficult.

I suppose the details are still sketchy at this point, but I have no idea how CloudFlare received a week's notice, and no one more important[1] knew of it until it was publicized. CloudFlare being the special group makes me suspicious of how it all went down.

[1] I'm not picking on CloudFlare, they have a huge footprint on the internet.

Re:My Heart Bleeds for OpenSSL by 0x0 on Tuesday April 08, 2014 @09:22PM (#7557182)
Apparently Akamai was also given early notice, from the OpenSSL team.

https://blogs.akamai.com/2014/04/heartbleed-faq-akamai-syste...

I wonder why the various linux distros like debian could not have been notified simultaneously.

Re:My Heart Bleeds for OpenSSL by jessaustin on Tuesday April 08, 2014 @09:58PM (#7557296)
Has distro notification caused problems in the past? E.g. patches posted early, emails forwarded, public discussion, etc.?
Re:My Heart Bleeds for OpenSSL by danielweber on Wednesday April 09, 2014 @09:05AM (#7558984)
No advance channel set up?

This stuff is always tricky, and I admittedly have a strong adverse reaction to the "just blow everything open, it will be lulzy when the web breaks" attitude.

To be on such a list you also need to have a positive prior record demonstrating your ability to keep your mouth shut, which is hard to prove.

Re:My Heart Bleeds for OpenSSL by IgorPartola on Wednesday April 09, 2014 @09:07AM (#7558993)
What about the Postgres bug from I think last year where instead of putting up a fancy looking site the people involved coordinated in secret with every major distro to release a patched package? That seemed to me to be much more professional. Or is this bug significantly different?
Re:My Heart Bleeds for OpenSSL by parennoob on Tuesday April 08, 2014 @08:54PM (#7557078)
> At that point, the incentives strongly favor the attackers, who will work quickly to join the in-crowd and exploit the window of time where they know how to exploit the flaw, and site operators don't know enough about it to take it seriously.

Has this sort of behaviour been observed for other vulnerabilities in the wild that can be cited? I would think that the patch is small enough that a co-ordinated deployment to all the distros could have been managed so that they had packages ready before attackers could exploit the vulnerability. Not sure that the correct solution is to announce it with a corporate blog post and a vanity web site instead.

Re:My Heart Bleeds for OpenSSL by frandroid on Tuesday April 08, 2014 @09:37PM (#7557224)
There's another name for the phenomenon described by tptacek above: insider trading. Plenty of examples in the wild. The more insiders know what's happening before the markets do, the more likely someone will act on it, or sell the information.
[deleted]
Re:My Heart Bleeds for OpenSSL by rdl on Tuesday April 08, 2014 @10:34PM (#7557394)
Someone still being on 0.9.8 and this not being vulnerable isn't too meaningful as an indicator. If they mysteriously went from 1.0.1f back to 0.9.8 without changing any other part of their configuration, that would be suspicious.

The lulzy thing about this bug is that people who are still on 0.9.8 aren't doing the right thing; they just got lucky on this one bug.

Re:My Heart Bleeds for OpenSSL by drewcrawford on Wednesday April 09, 2014 @04:52AM (#7558298)
> Has this sort of behaviour been observed for other vulnerabilities in the wild that can be cited?

Yes. The mailing list that was used as recently as 2011 to coordinate exactly this kind of issue was backdoored.

Further reading: http://www.openwall.com/lists/oss-security/2011/03/03/3