Further info: specifying a non-numeric HostName seems to solve the problem. In particular, it solved what seems to be a related problem. With the numeric HostName still in place, I tried $ ssh -oStrictHostKeyChecking=no somewhere @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ 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 xxx Please contact your system administrator. Add correct host key in /home/ross/.ssh/known_hosts to get rid of this message. Offending key in /home/ross/.ssh/known_hosts:140 Password authentication is disabled to avoid man-in-the-middle attacks. Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks. Port forwarding is disabled to avoid man-in-the-middle attacks. Permission denied (publickey,password).
When I changed HostName to a DNS type name, things worked: $ ssh -oStrictHostKeyChecking=no somewhere Warning: Permanently added 'foo.com' (RSA) to the list of known hosts. [EMAIL PROTECTED]'s password: Another theory: When HostName was an IP it was the same IP as used by the old system I was connecting too. Thus, if an entry were added to known_hosts, there would be two entries for the same key (the IP address). Maybe that was the source of the problem. Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
