RSA host key for ***** has changed and you have requested strict checking. Offending key in /home/user/.ssh/known_hosts:1 Please contact your system administrator.Īdd correct host key in /home/user/.ssh/known_hosts to get rid of this message. The fingerprint for the RSA key sent by the remote host is It is also possible that the RSA host key has just been changed. Someone could be eavesdropping on you right now (man-in-the-middle attack)! However, even with “ StrictHostKe圜hecking=no“, you may be refused to connect with the following warning message: WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! If you would like to bypass this verification step, you can set the “ StrictHostKe圜hecking” option to “ no” on the command line: $ ssh -o 'StrictHostKe圜hecking=no' option disables the prompt and automatically adds the host key to the ~/.ssh/known_hosts file. If your answer is ‘no’, the connection will be terminated. If your answer is ‘yes’, the SSH client continues login, and stores the host key locally in the file ~/.ssh/known_hosts.

Host verification failed.