SSH – Resolving Duplicate Keys in Known_Hosts for Same Server

known-hostssshssh-keys

I notice my local ~/.ssh/known_hosts file has two entries for the same machine on the local LAN:

 somemachine,192.168.1.200 ssh-rsa KEY...
 somemachine.search.domain ssh-rsa KEY...

It's the same key, the second one doesn't have the IP though. Is this just a result of having a search domain and so the known_hosts file must contain the "duplicate" key?

SSH won't detect it is visiting the same machine regardless of the hostname you attempt to connect with? 'SSH 192.168.1.200' does not request to create a new known_host so could I change the known_host to:

 somemachine,somemachine.search.domain,192.168.1.200 ssh-rsa KEY...

Best Answer

It is because you must have used ssh somemachine and ssh somemachine.search.domain in the past, which creates 2 different entries. In ubuntu this is how my entries were created, in any case.

Related Solutions

Ssh – Wiped out the known_hosts file on the server machine. Is it safe

It should create a new one automatically. You can always just touch a new one and then set permissions/ownership as needed (based off another one perhaps). I usually just remove the entries from known_hosts that are wrong and not whack the whole file.

Oh, and this belongs on SuperUser... :-)

SSH using public keys is not working

If you could copy/paste the lines from your log that you saw, that would help. A few guesses in the mean time:

Make sure that your permissions are correct.

chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

If you're trying to authenticate as root, you might need the following in your sshd_config:

PermitRootLogin without-password

I discovered this while setting up a Barracuda backup system for backing up a FreeBSD host. (On FreeBSD, its in /etc/ssh/sshd_config.)

Best Answer

Related Solutions

Ssh – Wiped out the known_hosts file on the server machine. Is it safe

SSH using public keys is not working

Related Topic