News for hackers. Stuff that matters.
Re:Heartbleed Update v3 by Sami_Lehtinen on Sunday April 13, 2014 @11:32PM (#7584381)
Why people are only talking about SSL keys? Because Heartbleed allowed to fetch any data, that could have also included SSH keys and or any other authentication credentials / information the server got, for itself or to other services. As example if your site got Facebook API keys it's possible that those have been leaking too.
Re:Heartbleed Update v3 by tptacek on Monday April 14, 2014 @01:17AM (#7584651)
No, your web server process memory does not include SSH keys.
Re:Heartbleed Update v3 by jbg_ on Sunday April 13, 2014 @11:43PM (#7584415)
Unless your web server makes SSH connections from some kind of in-process application, why would this bug allow SSH keys to leak?
Re:Heartbleed Update v3 by jevinskie on Monday April 14, 2014 @12:15AM (#7584512)
Is memory wiped with zeros by malloc/free in libc or in the kernel? If not, you're at risk.
Re:Heartbleed Update v3 by bzbarsky on Monday April 14, 2014 @12:23AM (#7584526)
Yes, it is. Leaking memory contents across processes would be a pretty serious bug in the kernel. So when your process asks the kernel for memory (via sbrk or mmap) the memory it gets is zeroed out.