18

How do I skip the "known_host" question the first time I connect to a machine via SSH with public/private keys?

  • Why was this marked as the duplicate when it predates the other question? – Jason Axelson Apr 13 '18 at 21:54
32

All the other current answers are missing the UserKnownHostsFile=/dev/null

If you just want to do it once you can use:

ssh -o StrictHostKeychecking=no hostname

If you want to do it repeatedly you should add something like the following to your ~/.ssh/config

Host 192.168.0.*
    StrictHostKeyChecking no
    UserKnownHostsFile=/dev/null

To configure this on OpenSSH for Windows simply replace /dev/null with NUL.

Good explanation from: http://linuxcommando.blogspot.com/2008/10/how-to-disable-ssh-host-key-checking.html

| improve this answer | |
  • 2
    I've been hunting for away to filter out a subnet for months (not actively), this is exactly what I've been wanting. We have a small development network with dhcp and our devices are always getting new IP address, this making connecting to them MUCH easier. Thanks! – Adam Lewis Sep 1 '15 at 15:24
13

Turn StrictHostKeyChecking off via ssh_config or command line options.

| improve this answer | |
  • /etc/ssh/ssh_config or ~/.ssh/config --- or whatever the equivalent is on windows if that's your client platform – Doug Harris Oct 14 '09 at 15:58
3

You can get the public key, add it to known_hosts file and then rehash it:

ssh-keyscan -t rsa hostname >> .ssh/known_hosts
ssh-keygen -H
rm .ssh/known_hosts.old
| improve this answer | |
2
$ ssh -o StrictHostKeychecking=no hostname

This will cause the check to be skipped and the remote host's key to automatically be added on first login. (There's also the option CheckHostIP, but it doesn't seem to actually disable the check for whether a key exists at all).

| improve this answer | |
  • 2
    I also like to use UserKnownHostsFile so that the signature isn't remembered on my system. A nice trick: ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeychecking=no hostname – metavida Apr 10 '12 at 21:54
2

This took me a while to find. The most common usecase I've seen is when you've got ssh tunnels to remote networks. All the solutions here produced warnings which broke my scripts (nagios).

The option I needed was:

NoHostAuthenticationForLocalhost yes

Which, as the name suggests also only applies to localhost.

| improve this answer | |
0

You can disable the checking, but of course that is less secure. In an ideal situation what you should do is get someone that already has access to the machine to grab it's public host key and tell ssh to use it. i.e.: take the output of:

cat /etc/ssh/ssh_host_rsa_key.pub

prepend the hostname of the machine, and add that line to the ~/.ssh/known_hosts file on your machine. You'll end up with something that looks like:

myhost.example.com ssh-rsa AAAAB3Netc...

Alternately, if you just want to grab the fingerprint of the key, which may be easier to transfer over a limited bandwidth channel (like a phone call), you can have your helper run:

ssh-keygen -lf /etc/ssh/ssh_host_rsa_key.pub
| improve this answer | |
0

If you just want to temporarily disable host checking, so you can log into a LiveCD system, for instance, rename ~/.ssh/known_hosts to something else, and then change it back when you're done.

| improve this answer | |
-2
  1. Add "StrictHostKeyChecking no" to /etc/ssh/ssh_config
  2. cd ~/.ssh
  3. rm known_hosts
  4. ln -s /dev/null known_hosts

Bingo

| improve this answer | |
  • 1
    You do know what kind of attack this question is supposed to prevent, do you? – vonbrand Mar 8 '13 at 18:19