Heartbleed disclosure timeline: who knew what and when

Re:Heartbleed disclosure timeline: who knew what and when by protomyth on Monday April 14, 2014 @06:43PM (#7589335)

How did Facebook get prior word but not Instagram?

I worry that Amazon wasn't given prior notice according to the timeline.

[ Parent | on HN ]

Re:Heartbleed disclosure timeline: who knew what and when by euank on Monday April 14, 2014 @07:00PM (#7589400)

Amazon Web Services was explicitly listed in the group of companies at the bottom that did not get notification.

[ Parent | on HN ]

Re:Heartbleed disclosure timeline: who knew what and when by Xorlev on Monday April 14, 2014 @07:25PM (#7589492)

It was a day after disclosure our ELBs were patched.

[ Parent | on HN ]

Re:Heartbleed disclosure timeline: who knew what and when by protomyth on Tuesday April 15, 2014 @08:26AM (#7591408)

Yes, and I am worried they did not get that notification

[ Parent | on HN ]

Re:Heartbleed disclosure timeline: who knew what and when by marcbarbosa on Monday April 14, 2014 @07:42PM (#7589550)

How Chromium did not get prior word from Google?

[ Parent | on HN ]

Re:Heartbleed disclosure timeline: who knew what and when by DannyBee on Monday April 14, 2014 @07:58PM (#7589604)

Chromium should not have been vulnerable to the bug, since it does not use openssl (last i looked, it used NSS).

Given that Adam Langley works with the chrome folks, i suspect it did not end up needing it in the end :)

[ Parent | on HN ]

Re:Heartbleed disclosure timeline: who knew what and when by gsnedders on Tuesday April 15, 2014 @08:22AM (#7591403)

I suspect, given the email gave no details, they had no knowledge of whether it was the same bug or not.

[ Parent | on HN ]

Re:Heartbleed disclosure timeline: who knew what and when by brown9-2 on Tuesday April 15, 2014 @11:31AM (#7592327)

That seems like a Facebook internal issue. No reason why they can't be expected to share info with entities that they own.

[ Parent | on HN ]