News for hackers. Stuff that matters.
Re:The Heartbleed Bug by sexmonad on Monday April 07, 2014 @05:18PM (#7549589)
Update to 1.0.1g, redo all crypto. That is, revoke certs and keys and regenerate.
Re:The Heartbleed Bug by munger on Tuesday April 08, 2014 @12:01PM (#7554206)
What you probably want is to re-key your cert, do not revoke it. Revoking with some CA's (such as GoDaddy) means to essentially cancel the remainder of the valid date forever and requires purchasing a new cert to secure the same domain. You are forfeiting the rest of its value.

When you re-key, it will automatically deactivate the previous cert and is free. It also gives you the opportunity to update to SHA-2 or increase the key to 2048 bit, which you should do unless you have unusual and extreme legacy support needs (and must keep SHA-1 a while longer).

Re:The Heartbleed Bug by stderr5150 on Wednesday April 09, 2014 @12:16AM (#7557618)
I disagree. Revoking the certificate is a requirement. If you re-key without revoking, that means someone who has stolen your key could impersonate you until the validity period expires. So revoking is a needed if you want to inoculate yourself against a potential active man-in-the-middle attack.

If you want to be secure, make sure the certificate based on your old key is showing up in the certificate revocation list (CRL), and/or any online certificate status protocol (OCSP) servers it specifies.

Re:The Heartbleed Bug by ehPReth on Monday April 07, 2014 @10:08PM (#7551024)
Just a note to others: all crypto includes things like SSH keys, SSH host keys, and GPG keys. Anything in memory could have been read.
Re:The Heartbleed Bug by mpyne on Monday April 07, 2014 @10:45PM (#7551159)
Well, I don't think it's anything in memory, but whatever was up to 64k from wherever the downloaded packet was put in userspace (Edit: Er, 64k at a time, but the attacker can try again over and over). Since the kernel should be handing only zeroed pages to userspace to use as a buffer then it should only be memory used by the process using openssl at risk.

The big problem is that this is still a gigantic range of processes (and possible memory buffer contents). But SSH at least would appear to be fine, unless you've ever transferred an SSH key over TLS using OpenSSL.

Re:The Heartbleed Bug by ehPReth on Tuesday April 08, 2014 @01:34PM (#7554822)
Apologies, my mistake. I'd redact my comment if I was able to.
Re:The Heartbleed Bug by MichaelGG on Tuesday April 08, 2014 @04:13AM (#7552077)
How would a TLS webserver read the memory of sshd? Processes shouldn't generally have everything mapped in.