Hi, Yes, ssh does not automatically translate cvs.sv.gnu.org to cvs.savannah.gnu.org.
If you think the documentation needs to explain this, you can edit the page :) -- Sylvain On Wed, Jun 18, 2008 at 10:51:07PM -0400, Nicodemo Alvaro wrote: > The documentation referenced below is here: > http://savannah.gnu.org/maintenance/SshAccess > > The documentation says to use this command, but it turns out nothing. > > ~> ssh-keygen -l -f ~/.ssh/known_hosts | grep cvs.sv.gnu.org > > Without grep I find cvs.savannah.gnu.org > > ~> ssh-keygen -l -f ~/.ssh/known_hosts > 2048 66:5d:53:5e:a3:c8:8e:cc:da:39:14:e3:f8:d4:f1:80 [localhost]:2222 > 1024 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5 > cvs.savannah.gnu.org,199.232.41.69 > 2048 d8:d6:37:9a:50:57:32:10:9f:c9:8b:91:e0:92:0d:e2 localhost > > > ~> cvs -z3 -d:ext:[EMAIL PROTECTED]:/web/savane-cleanup > co savane-cleanup > cvs.savannah.gnu.org: Protocol not available > cvs [checkout aborted]: end of file from server (consult above messages if > any) > ~> ssh -v [EMAIL PROTECTED] > OpenSSH_4.7p1, OpenSSL 0.9.8h 28 May 2008 > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: Connecting to cvs.savannah.gnu.org [199.232.41.69] port 22. > debug1: Connection established. > debug1: identity file /home/nick/.ssh/identity type -1 > debug1: identity file /home/nick/.ssh/id_rsa type -1 > debug1: identity file /home/nick/.ssh/id_dsa type 2 > debug1: Remote protocol version 2.0, remote software version > OpenSSH_4.3p2 Debian-9etch2 > debug1: match: OpenSSH_4.3p2 Debian-9etch2 pat OpenSSH* > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_4.7 > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: server->client aes128-cbc hmac-md5 none > debug1: kex: client->server aes128-cbc hmac-md5 none > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY > debug1: Host 'cvs.savannah.gnu.org' is known and matches the RSA host key. > debug1: Found key in /home/nick/.ssh/known_hosts:3 > debug1: ssh_rsa_verify: signature correct > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug1: SSH2_MSG_NEWKEYS received > debug1: SSH2_MSG_SERVICE_REQUEST sent > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug1: Authentications that can continue: publickey > debug1: Next authentication method: publickey > debug1: Trying private key: /home/nick/.ssh/identity > debug1: Trying private key: /home/nick/.ssh/id_rsa > debug1: Offering public key: /home/nick/.ssh/id_dsa > debug1: Server accepts key: pkalg ssh-dss blen 433 > debug1: PEM_read_PrivateKey failed > debug1: read PEM private key done: type <unknown> > Enter passphrase for key '/home/nick/.ssh/id_dsa': > debug1: read PEM private key done: type DSA > debug1: Authentication succeeded (publickey). > debug1: channel 0: new [client-session] > debug1: Entering interactive session. > debug1: Requesting authentication agent forwarding. > Last login: Sat Jun 7 18:22:25 2008 from > pool-71-254-223-164.hrbgpa.east.verizon.net > You tried to execute: > Sorry, you are not allowed to execute that command. > debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 > debug1: channel 0: free: client-session, nchannels 1 > Connection to cvs.savannah.gnu.org closed. > debug1: Transferred: stdin 0, stdout 0, stderr 44 bytes in 0.4 seconds > debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 123.8 > debug1: Exit status 1
