Gunnar_Zarncke comments on My Heartbleed learning experience and alternative to poor quality Heartbleed instructions. - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (31)
For #1, "I reacted immediately" and "I reacted when the urgency became evident" are probably the same thing for most people. I heard about the bug 20 minutes after it was announced, from the Cloudflare blog of all places. Not even USN had posted about it. I patched my servers within an hour, and spent the next 5 hours waiting for my CA to respond to my revocation and re-key requests. Apparently they were inundated.
On the bright side, I prepared for security issues like this. I used multi-factor auth for our admin tools and perfect forward secrecy cipher suites for our TLS. Even with our private key, previously recorded traffic cannot be decrypted. And if an attacker got ahold of our passwords, they would still need to steal our YubiKeys to get access to our admin tools.
Hooray for being paranoid about security.
Note that a sysadmin might e.g. react immediately to patch their company's servers, revoke keys, etc., but be far more lax about changing their own passwords.
Meanwhile, and possibly distorting the poll, I still have not reacted despite wanting to do so because my internet connection is currently a wet piece of string (slow GPRS). Perhaps there should be an option for "I couldn't react"?
Not offered answer 1: I acted immediately by not logging in to anything, but not really doing anything else Not offered answer 2: I thought I told someone, but she didn't remember later so maybe I didn't?
How long questions: The quickest folks would have it taken care of in hours, the slowest in years. When is it really taken care of?