Return to Answer

replaced http://superuser.com/ with https://superuser.com/

Source Link

edited Mar 20, 2017 at 10:18

Here is a script that you can use to see if your vulnerable or not: http://pastebin.com/1HxgWpTN

Here you also have an answers about ssh : http://superuser.com/questions/739349/does-heartbleed-affect-ssh-keys https://superuser.com/questions/739349/does-heartbleed-affect-ssh-keys

No, Heartbleed doesn't really affect SSH keys, so you probably don't need to replace the SSH keys you've been using.

First, SSL and SSH are two different security protocols for two different uses. Likewise, OpenSSL and OpenSSH are also two completely different software packages, despite the similarities in their names.

Second, the Heartbleed exploit causes the vulnerable OpenSSL TLS/DTLS peer to return a random 64kB of memory, but it's almost certainly limited to memory accessible to that OpenSSL-using process. If that OpenSSL-using process doesn't have access to your SSH private key, then it can't leak it via Heartbleed.

Here is a script that you can use to see if your vulnerable or not: http://pastebin.com/1HxgWpTN

Here you also have an answers about ssh : http://superuser.com/questions/739349/does-heartbleed-affect-ssh-keys

No, Heartbleed doesn't really affect SSH keys, so you probably don't need to replace the SSH keys you've been using.

First, SSL and SSH are two different security protocols for two different uses. Likewise, OpenSSL and OpenSSH are also two completely different software packages, despite the similarities in their names.

Second, the Heartbleed exploit causes the vulnerable OpenSSL TLS/DTLS peer to return a random 64kB of memory, but it's almost certainly limited to memory accessible to that OpenSSL-using process. If that OpenSSL-using process doesn't have access to your SSH private key, then it can't leak it via Heartbleed.

Here is a script that you can use to see if your vulnerable or not: http://pastebin.com/1HxgWpTN

Here you also have an answers about ssh : https://superuser.com/questions/739349/does-heartbleed-affect-ssh-keys

No, Heartbleed doesn't really affect SSH keys, so you probably don't need to replace the SSH keys you've been using.

First, SSL and SSH are two different security protocols for two different uses. Likewise, OpenSSL and OpenSSH are also two completely different software packages, despite the similarities in their names.

Second, the Heartbleed exploit causes the vulnerable OpenSSL TLS/DTLS peer to return a random 64kB of memory, but it's almost certainly limited to memory accessible to that OpenSSL-using process. If that OpenSSL-using process doesn't have access to your SSH private key, then it can't leak it via Heartbleed.

Source Link

created Apr 9, 2014 at 10:51

Boogy

Here is a script that you can use to see if your vulnerable or not: http://pastebin.com/1HxgWpTN

Here you also have an answers about ssh : http://superuser.com/questions/739349/does-heartbleed-affect-ssh-keys

No, Heartbleed doesn't really affect SSH keys, so you probably don't need to replace the SSH keys you've been using.

First, SSL and SSH are two different security protocols for two different uses. Likewise, OpenSSL and OpenSSH are also two completely different software packages, despite the similarities in their names.

Second, the Heartbleed exploit causes the vulnerable OpenSSL TLS/DTLS peer to return a random 64kB of memory, but it's almost certainly limited to memory accessible to that OpenSSL-using process. If that OpenSSL-using process doesn't have access to your SSH private key, then it can't leak it via Heartbleed.