Use a opção StrictHostKeyChecking, por exemplo:
ssh -oStrictHostKeyChecking=no $h uptime
Esta opção também pode ser adicionada a ~ / .ssh / config, por exemplo:
Host somehost
Hostname 10.0.0.1
StrictHostKeyChecking no
Observe que, quando as chaves do host forem alteradas, você receberá um aviso, mesmo com essa opção:
$ ssh -oStrictHostKeyChecking=no somehost uptime
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
31:6f:2a:d5:76:c3:1e:74:f7:73:2f:96:16:12:e0:d8.
Please contact your system administrator.
Add correct host key in /home/peter/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/peter/.ssh/known_hosts:24
remove with: ssh-keygen -f "/home/peter/.ssh/known_hosts" -R 10.0.0.1
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
ash: uptime: not found
Se seus hosts não forem reinstalados com freqüência, você poderá tornar isso menos seguro (mas mais conveniente para as chaves de host que mudam com frequência) com a opção -oUserKnownHostsFile=/dev/null
. Isso descarta todas as chaves de host recebidas para que nunca gerem o aviso.
Com o 18.04, há uma nova possibilidade: StrictHostKeyChecking=accept-new
. De man 5 ssh_config
:
If this flag is set to “accept-new” then ssh will automatically
add new host keys to the user known hosts files, but will not
permit connections to hosts with changed host keys. If this flag
is set to “no” or “off”, ssh will automatically add new host keys
to the user known hosts files and allow connections to hosts with
changed hostkeys to proceed, subject to some restrictions.