Hardware Reference
In-Depth Information
Discussion
Sometimes, when connecting via SSH, you will get an error like this:
host$ ssh root@192.168.7.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 ECDSA key sent by the remote host is
1b:dc:bc:c6:8f:87:f7:de:30:97:a4:7b:84:9d:84:ad.
Please contact your system administrator.
Add correct host key in /home/yoder/.ssh/known_hosts to get rid of
this message.
Offending ECDSA key in /home/yoder/.ssh/known_hosts:3
remove with: ssh-keygen -f "/home/yoder/.ssh/known_hosts" -R
192.168.7.2
ECDSA host key for 192.168.7.2 has changed, you have requested strict
checking.
Host key verification failed.
A quick fix is to follow the directions in the error:
host$ ssh-keygen -f "/home/yoder/.ssh/known_hosts" -R 192.168.7.2
A longer-term solution is to create an SSH configuration file. Add the following code to a
file called ~/.ssh/config :
Host 192.168.7.2
User root
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
The UserKnownHostsFile parameter says to check /dev/null for a list of hosts it
knows, but /dev/null is a file that is always empty, so SSH will assume it doesn't know
Search WWH ::




Custom Search