Arch Linux

alphaniner

Member

From: Ancapistan

Registered: 2010-07-12

Posts: 2,810

ssh key hashing problem

I have a machine with numerous OSs, all of which get the same static IP from DHCP for the 'admin' NIC.  Using ssh, I get the following error:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    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
6c:0b:ae:fa:e0:b4:95:ad:6a:32:ce:13:29:5c:a1:0c.
Please contact your system administrator.
Add correct host key in /home/testing/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/testing/.ssh/known_hosts:1
RSA host key for 199.200.1.100 has changed and you have requested strict checking.
Host key verification failed.

Note the second to last line.  So I turn off strict checking and I still get the error, this time with a different 'excuse':

...
Password authentication is disabled to avoid man-in-the-middle attacks.
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
Permission denied (publickey,keyboard-interactive).

I tried setting public key to no; that had no effect.  I know I can delete the hashed key, but that's not a practical solution.  So how do I get ssh to permanently ignore the issue, whether for just this one IP, or all together if necessary?  Thanks.

Last edited by alphaniner (2012-01-26 14:19:17)

---

But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner