14 Mar 2016

Fix: Remote Host Identification has changed

WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@     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
51:82:00:1c:7e:6f:ac:ac:de:f1:53:08:1c:7d:55:68.
Please contact your system administrator.
Add correct host key in /Users/BaseZap/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/BaseZap/.ssh/known_hosts:12
RSA host key for 102.121.14.75 has changed and you have requested strict checking.
Host key verification failed.

This message may be due to change of key. Was the system reinstalled? You may see this message after overwriting your key. And it probably left you wondering if this is usual. Yes! It is. For the reason that you updated your key, getting this message is normal.

What to do?

Just edit ~/.ssh/known_hosts and delete line 12, as the message pointed you

Offending RSA key in /Users/isaacalves/.ssh/known_hosts:12

Or use ssh-keygen to delete the invalid key  (preferred solution)

ssh-keygen -R "your domain name or IP"

eg:  ssh-keygen -R "basezap.com"

The issue on the client side host file will be fixed. 🙂

After this, when you will try to use SSH to connect to the host, you will see this message:

The authenticity of host ‘[your host information]’ can’t be established.
RSA key fingerprint is 06:ea:f1:f8:db:75:5c:0c:af:15:d7:99:2d:ef:08:2a.
Are you sure you want to continue connecting (yes/no)?

Type ‘Yes’ and move ahead with SSH logic procedures.