something wicked this way comes
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
|
00:28:52 ~ $ ssh fujipi
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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
79:d6:df:b5:de:1b:5a:5d:41:0a:40:xx:xx:xx:xx:xx.
Please contact your system administrator.
Add correct host key in /Users/cherron/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/cherron/.ssh/known_hosts:36
RSA host key for fujipi has changed and you have requested strict checking.
Host key verification failed.
|
When I ping fujipi, it reports the correct IP – it’s in my hosts file! For the record, the host key should not have changed.
Turns out, there was no foul play going on. It was a bug in VirtualBox, Mavericks network stack, my router, or some combination thereof. Strangely, running a Linux VM in VBox caused an attempt to ssh to an actual Linux system elsewhere on my netowrk to instead be directed to the VM.
After checking some current status data on the router, it looked like my Movericks host was trying to assume the same IP as the physical Linux system. Then I remembered that an SSH connection was abruptly disconnected from my VM to an outside box. Something about VirtualBox’s bridged interface for a Linux VM caused it to try to take an unavailable IP on my local network.
After I shutdown the VM, I could then SSH normally to the local Linux box.
About The Author
Charlie Herron
Denizen of Portland, Maine; tech jack; lover / hater / whatever; philosophical dabbler. http://twitter.com/realgeek