I would like to disable strict host key checking in ssh
for Ubuntu 11.04. How to do it?
7 Answers
In your ~/.ssh/config
(if this file doesn't exist, just create it):
Host *
StrictHostKeyChecking no
This will turn it off for all hosts you connect to. You can replace the *
with a hostname pattern if you only want it to apply to some hosts.
Make sure the permissions on the file restrict access to yourself only:
sudo chmod 400 ~/.ssh/config
-
7Make one - the entire contents of the file are in my quote above. Note it's in the
.ssh
subdirectory of your homedir as well.– CaesiumDec 14, 2011 at 14:44 -
Is the indentation required? My entries look like blocks divided by a empty line. Jun 20, 2017 at 10:04
-
18This is unwise in many cases, often you just want to disable it once:
ssh -o UserKnownHostsFile=/dev/null
Aug 29, 2017 at 9:34 -
3mkdir -p ~/.ssh && echo "Host *" > ~/.ssh/config && echo " StrictHostKeyChecking no" >> ~/.ssh/config Apr 25, 2018 at 12:24
-
Awesome, I was stuck in fixing ~/.ssh/known_hosts but it never existed. Luckily I found this thread and can log in now. I'm just wondering how can i log in to other machine but not just one specific type of machine which i launched by shared ami from another aws account. Thanks– SatysMay 6, 2018 at 12:08
Rather than adding it to your ~/.ssh/config
file for all Host *, it would be a safer to specify a particular host.
You can also pass a parameter on the command-line like this:
ssh -o StrictHostKeyChecking=no yourHardenedHost.com
This will automatically add the host key to your known_hosts file if it's not already there.
If there's a mismatch, it will display a big warning and not update known_hosts. It will also disable password-based authentication to prevent MITM attacks. Private key authentication will still automatically get through though, which you may not want.
-
1Note that you generally only need to do this once per host since it says this the first time:
Warning: Permanently added 'frxxx.blaps.net,10.11.12.13' (RSA) to the list of known hosts.
– MarkHuJul 24, 2013 at 0:49 -
45That won't work. It should be
ssh -o UserKnownHostsFile=/dev/null
instead. Oct 29, 2014 at 2:51 -
5@qwertzguy It does work. Your option will make it so that the host key is lost each time, which is useful and more secure, but not what the question asked for. Nov 30, 2015 at 0:04
-
3use both works for me, ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no Nov 12, 2017 at 5:35
-
2
It's worth pointing out that setting in your ssh config:
StrictHostKeyChecking no
Will mean hostkeys are still added to .ssh/known_hosts - you just won't be prompted about whether you trust them, but should hosts change I'm willing to bet you'll get the big warning about it. You can work around this problem by adding another parameter:
UserKnownHostsFile /dev/null
This will add all these "newly discovered" hosts to the trash bin. If a host key changes, no troubles.
I would be remiss not to mention that circumventing these warnings on hostkeys has obvious security ramifications - you should be careful that you're doing it for the right reasons & that what you're connecting to actually is what you mean to connect to and not a malicious host, since at this point you've eroded a major part of the security in ssh as a solution.
For example if you were to try and set this with the commandline, the full command would be:
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null user@host
That would be silly though - given that the working examples above for ssh config files is likely to make more sense in all cases.
-
1
-
1I think this is the right answer. This works well for connecting to hosts on a private local network. Jan 14, 2015 at 14:39
-
10Could be convenient to have an alias to
ssh -o StrictHostKeyChecking=no -o UserKnownHostFiles=/dev/null user@host
. In my case I useissh
to connect to hosts where I know the host key changes. May 2, 2016 at 13:53 -
2@ecerulm - just a small typo: it's
UserKnownHostsFile
notUserKnownHostFiles
. Oct 2, 2017 at 10:16 -
3@LeeMeador There isn't a
known_hosts
file in your Docker containers because nobody put one there. Not because there can't be one or never is one. There can be one. You can copy one in at build time, or mount one at docker run time, or fetch one from inside the container using another secure mechanism. If this security issue is important enough to your organization, then you can create a discovery and delivery system in your CI/CD processes to have an updatedknown_hosts
file in your Docker images.– ErikEJul 13, 2020 at 9:50
FYI. I prefer to disable host checking just when using cssh.
alias cssh='ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null'
-
1
-
1
-
1
-
2
alias relay='ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null [email protected] -p 2222'
work for me Jul 25, 2018 at 8:12
If you want to disable on a one time basis use:
ssh -o UserKnownHostsFile=/dev/null
That will work also if the host key changes and will make sure not to save the key as trusted for added security.
From what it sounds like,
NoHostAuthenticationForLocalhost yes
may be good enough, for you. AND you'd still be able to maintain that semblance of security.
https://askubuntu.com/a/87452/129227 suggest to modify the config file which helps. But instead of opening things up for any host I wanted this to be done per host. The script below helps automating the process:
example call
./sshcheck somedomain site1 site2 site3
sshcheck script
#!/bin/bash
# WF 2017-08-25
# check ssh access to bitplan servers
#ansi colors
#http://www.csc.uvic.ca/~sae/seng265/fall04/tips/s265s047-tips/bash-using-colors.html
blue='\033[0;34m'
red='\033[0;31m'
green='\033[0;32m' # '\e[1;32m' is too bright for white bg.
endColor='\033[0m'
#
# a colored message
# params:
# 1: l_color - the color of the message
# 2: l_msg - the message to display
#
color_msg() {
local l_color="$1"
local l_msg="$2"
echo -e "${l_color}$l_msg${endColor}"
}
#
# error
#
# show an error message and exit
#
# params:
# 1: l_msg - the message to display
error() {
local l_msg="$1"
# use ansi red for error
color_msg $red "Error: $l_msg" 1>&2
exit 1
}
#
# show the usage
#
usage() {
echo "usage: $0 domain sites"
exit 1
}
#
# check the given server
#
checkserver() {
local l_server="$1"
grep $l_server $sconfig > /dev/null
if [ $? -eq 1 ]
then
color_msg $blue "adding $l_server to $sconfig"
today=$(date "+%Y-%m-%d")
echo "# added $today by $0" >> $sconfig
echo "Host $l_server" >> $sconfig
echo " StrictHostKeyChecking no" >> $sconfig
echo " userKnownHostsFile=/dev/null" >> $sconfig
echo "" >> $sconfig
else
color_msg $green "$l_server found in $sconfig"
fi
ssh -q $l_server id > /dev/null
if [ $? -eq 0 ]
then
color_msg $green "$l_server accessible via ssh"
else
color_msg $red "ssh to $l_server failed"
color_msg $blue "shall I ssh-copy-id credentials to $l_server?"
read answer
case $answer in
y|yes) ssh-copy-id $l_server
esac
fi
}
#
# check all servers
#
checkservers() {
me=$(hostname -f)
for server in $(echo $* | sort)
do
os=`uname`
case $os in
# Mac OS X
Darwin*)
pingoption=" -t1";;
*) ;;
esac
pingresult=$(ping $pingoption -i0.2 -c1 $server)
echo $pingresult | grep 100 > /dev/null
if [ $? -eq 1 ]
then
checkserver $server
checkserver $server.$domain
else
color_msg $red "ping to $server failed"
fi
done
}
#
# check configuration
#
checkconfig() {
#https://askubuntu.com/questions/87449/how-to-disable-strict-host-key-checking-in-ssh
if [ -f $sconfig ]
then
color_msg $green "$sconfig exists"
ls -l $sconfig
fi
}
sconfig=~/.ssh/config
case $# in
0) usage ;;
1) usage ;;
*)
domain=$1
shift
color_msg $blue "checking ssh configuration for domain $domain sites $*"
checkconfig
checkservers $*
;;
esac
-
2
grep $l_server $sconfig > /dev/null; if [ $? -eq 1 ]; then
should be replaced withif ! grep -q "$l_server" "$sconfig"; then
. 1) Don't check exit codes unless required, instead just useif
directly. 2) grep has a-q
option. Use it instead of> /dev/null
. 3) All environment variable expansion should be double-quoted. Also, consider avoiding abbreviations and consider naming compound words likecheckserver
ascheck_server
orcheckServer
so IDEs with spell check don't complain.– ErikEJul 13, 2020 at 9:58 -
@ErikE - please post your improved version - I'll happily upvote it. Jul 13, 2020 at 12:20
-
ssh -o UserKnownHostsFile=/dev/null