« Previous | Next»

Debian OpenSSL Issue on Arm[el] (Thecus, NSLU etc)?

Posted by coldtobi | 16 May, 2008, 18:43 By the way, the OpenSSL "issue" is also valid for the other debian ports, like the Thecus.

However, I read the quoted section from Metasploit

This will generate a new OpenSSH 1024-bit DSA key with the value of
getpid() always returning the number "1". We now have our first
pre-generated SSH key. If we continue this process for all PIDs up to
32,767 and then repeat it for 2048-bit RSA keys, we have covered the
valid key ranges for x86
systems running the buggy version of the OpenSSL library. With this key
set, we can compromise any user account that has a vulnerable key
listed in the authorized_keys file. This key set is also useful
for decrypting a previously-captured SSH session, if the SSH server was
using a vulnerable host key. Links to the pregenerated key sets for
1024-bit DSA and 2048-bit RSA keys (x86) are provided in the downloads section below.


the way, that the compiled list of compromised keys is only valid for a specific architecure. As ssh-vulnkey is using compiaring the keys against a blacklist, it might be a good idea to regenerate these keys. Even if I am wrong, it is better to be safe than sorry ;-)


(I've regenerated them already. Here's how to (as root, on the device). I assume that you know avoiding being locked-out, right? You'd want to open a spare ssh connection to repair things you break?

ssh-keygen -t rsa /etc/ssh/ssh_host_rsa_key
ssh-keygen -t dsa /etc/ssh/ssh_host_dsa_key
ssh-keygen -t rsa1 /etc/ssh/ssh_host_key

  _ASIP_

Thecus N2100 | Comments (0) | Trackbacks (0)

Related Articles:

0 Comments | "Debian OpenSSL Issue on Arm[el] (Thecus, NSLU etc)?" »