Øystein Johansen <[EMAIL PROTECTED]> writes: > I lied! I was just about to commit it as I got a technical problem. The > cvs has changed location, and things wasn't as easy as I first assumed.
> Jon? (or other windows builders and cvs users?) Have you had the same > problem? Have you solved it? > The problem is ..... > C:\gnubg-gtk28\gnubg>cvs -z3 > -d:ext:[EMAIL PROTECTED]:/sources/gnubg co gnubg > 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 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5 > 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". [...] > I'm not able to press 'y' for yes. Can I 'trust' the connection in some > kind of setting in putty? It may be as simple as just connecting directly to cvs.sv.gnu.org with PuTTY and accepting the key. I think what's preventing you from doing that here with CVS is that CVS doesn't understand what PuTTY is complaining about and getting confused by its output. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
