On Wed, 19 Nov 2003, Colonel
wrote:
>If anyone is using Anonymizer's SSH service, like me, you may have received
>a big bold warning when trying to logon to their cyberpass.net server today.
>It said: 'WARNING - THE HOST IDENTIFICATION HAS CHANGED!" and goes on to
>list 3 reasons why this may have happened.
>
>1) that Anonymizer has changed their host name (key or IP address), or
>2) the service has been upgraded from SSH1 to SSH2, or
>3) (their caps) SOMEONE COULD BE EVESDROPPING ON YOU RIGHT NOW
>(man-in-the-middle-attack)!
>
>It further says: "It is not recommended to connect until you have
>contacted the host administrator (Anonymizer) to find out why the host
>identification has changed."
>
>Then it asks: "Do you want to continue with the connection?" You then are
>presented with 3 hot buttons. YES -- NO (default) -- and HELP
>
>If HELP is clicked on and you use F-Secure tunneller, the help files warn
>you against trying to proceed with the connection until you contact
>Anonymizer and recommends you do so by phone.
>
>Well, the initial heart palpatations calmed down when I realized that there
>was really no reason for an intruder to try to pose as the remote host. I
>spent considerable time being in the cue on the phone with Anonymizer
>Support before getting a real live person to talk to. He explained that they
>indeed changed host keys (this should make Dr. Who happy) and that they were
>powering down the old server and bringing up the new server and that I
>should choose the YES button and proceed to continue to make the connection
>to the new host server using the new key.
>
you also request key fingerprint from real live person for compare -
right ? !!
else you do only halfbaked protocol