#2244 Unable to login to autoqa01.phx2
Closed: Fixed None Opened 13 years ago by jlaska.

Since qa01.phx2 was renamed to autoqa01.phx2, I'm no longer able to login. It seems that known_hosts entry for that system needs to be updated?

{{{
$ ssh autoqa01
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for autoqa01 has changed,
and the key for the according IP address 10.5.126.48
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /etc/ssh/ssh_known_hosts:50
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
2c:60:05:c4:73:41:3e:fb:3d:02:59:fa:3d:47:56:49.
Please contact your system administrator.
Add correct host key in /home/fedora/jlaska/.ssh/known_hosts to get rid of this message.
Offending key in /etc/ssh/ssh_known_hosts:83
RSA host key for autoqa01 has changed and you have requested strict checking.
Host key verification failed.
}}}

I'm able to manually login by disabling StrictHostKeyChecking, but it seems the system-wide ''/etc/ssh/ssh_known_hosts'' file needs to be updated?

{{{
$ ssh -o StrictHostKeyChecking=no root@autoqa01
}}}


Login to comment on this ticket.

Metadata