Comment 1 for bug 238869

Revision history for this message
Vernon Cole (vernondcole) wrote : Re: codehosting ssh host key not verifiable

I have spent all afternoon hunting this one down, including installing a new version of Bazaar, registering every conceivable key in launchpad, etc. Very frustrating.
  I am running Windows XP professional with PuTTY 0.60 and four versions of Python. For simplicity, I installed Bazaar from bzr-setup-1.9.exe.

v v v v v Begin screen dump v v v v v v
D:\>bzr branch lp:storm
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 1024 9d:38:3a:63:b1:d5:6f:c4:44:67:53:49:2e:ee:fc:89
Connection abandoned.
bzr: ERROR: Connection closed: please check connectivity and permissions (and tr
y -Dhpss if further diagnosis is required)
^ ^ ^ ^ ^ ^ end screen dump ^ ^ ^ ^ ^ ^ ^ ^

Note that I have no way of *accepting* a connection, nor do I know *where* the connection is going. When I finally located this bug report, it gave me enough information to concoct the following workaround:

v v v v v v begin workaround v v v v v v v
D:\>plink <email address hidden> ls
The server's host key is not cached in the registry. You
have no guarantee that the server is the computer you
think it is.
The server's rsa2 key fingerprint is:
ssh-rsa 1024 9d:38:3a:63:b1:d5:6f:c4:44:67:53:49:2e:ee:fc:89
If you trust this host, enter "y" to add the key to
PuTTY's cache and carry on connecting.
If you want to carry on connecting just once, without
adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the
connection.
Store key in cache? (y/n) y
Not allowed to execute 'ls'.
^ ^ ^ ^ ^ ^ end workaround ^ ^ ^ ^ ^ ^ ^ ^ ^

This should be taken care of at installation time somehow.
--
Vernon Cole