drv> I think I need an ssh expert. I can't update anymore: for Sorry, I don't have one either. drv> some reason, ssh doesn't handle my key and asks me for a drv> password. Could this be related to my recent switch to ssh 2 drv> ? Yes, I think so. Try this in your ~/.ssh/config: Host cvs.xemacs.org ForwardAgent no ForwardX11 no Protocol 1 User martinb drv> Here's a transcript of an attempt to cvs update (not much drv> information about the failure :-(): Well, following lines confirm that protocol 2 is being used. debug1: Found key in /home/didier/.ssh/known_hosts2:2 debug1: try privkey: /home/didier/.ssh/id_rsa debug1: try privkey: /home/didier/.ssh/id_dsa I use OpenSSH_2.9p1, SSH protocols 1.5/2.0, OpenSSL 0x0090600f of CYGWIN_NT-5.0 D5DC120J 1.3.2(0.39/3/2) 2001-05-20 23:28 i686 unknown and above config works fine with cvs -f -z3 -d:ext:martinb＠cvs.xemacs.org:/usr/CVSroot commit ... Hope this helps, Adrian drv> runsocks cvs update drv> OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f drv> debug1: Reading configuration data /home/didier/.ssh/config drv> debug1: Applying options for * drv> debug1: Reading configuration data /etc/ssh/ssh_config drv> debug1: Seeding random number generator drv> debug1: Rhosts Authentication disabled, originating port will not be trusted. drv> debug1: restore_uid drv> debug1: ssh_connect: getuid 17030 geteuid 17030 anon 1 drv> debug1: Connecting to cvs.xemacs.org [208.25.65.6] port 22. drv> debug1: temporarily_use_uid: 17030/17000 (e=17030) drv> debug1: restore_uid drv> debug1: temporarily_use_uid: 17030/17000 (e=17030) drv> debug1: restore_uid drv> debug1: Connection established. drv> debug1: identity file /home/didier/.ssh/identity type 0 drv> debug1: identity file /home/didier/.ssh/id_rsa type -1 drv> debug1: identity file /home/didier/.ssh/id_dsa type -1 drv> debug1: Remote protocol version 1.99, remote software version 2.0.13 (non-commercial) drv> debug1: match: 2.0.13 (non-commercial) pat ^2\.0\.1[3-9] drv> Enabling compatibility mode for protocol 2.0 drv> debug1: Local version string SSH-2.0-OpenSSH_2.9p2 drv> debug1: SSH2_MSG_KEXINIT sent drv> debug1: SSH2_MSG_KEXINIT received drv> debug1: kex: server->client 3des-cbc hmac-md5 none drv> debug1: kex: client->server 3des-cbc hmac-md5 none drv> debug1: dh_gen_key: priv key bits set: 191/384 drv> debug1: bits set: 515/1024 drv> debug1: sending SSH2_MSG_KEXDH_INIT drv> debug1: expecting SSH2_MSG_KEXDH_REPLY drv> debug1: Host 'cvs.xemacs.org' is known and matches the DSA host key. drv> debug1: Found key in /home/didier/.ssh/known_hosts2:2 drv> debug1: bits set: 519/1024 drv> debug1: len 40 datafellows 74335 drv> debug1: ssh_dss_verify: signature correct drv> debug1: kex_derive_keys drv> debug1: newkeys: mode 1 drv> debug1: SSH2_MSG_NEWKEYS sent drv> debug1: waiting for SSH2_MSG_NEWKEYS drv> debug1: newkeys: mode 0 drv> debug1: SSH2_MSG_NEWKEYS received drv> debug1: done: ssh_kex2. drv> debug1: send SSH2_MSG_SERVICE_REQUEST drv> debug1: buggy server: service_accept w/o service drv> debug1: got SSH2_MSG_SERVICE_ACCEPT drv> debug1: authentications that can continue: publickey,password, drv> debug1: next auth method to try is publickey drv> debug1: try privkey: /home/didier/.ssh/id_rsa drv> debug1: try privkey: /home/didier/.ssh/id_dsa drv> debug1: next auth method to try is password drv> didierv(a)cvs.xemacs.org's password: cvs [update aborted]: received interrupt signal drv> zsh: exit 1 runsocks cvs update drv> -- drv> Didier Verna, didier(a)lrde.epita.fr, http://www.lrde.epita.fr/~didier drv> EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 53 14 59 47 drv> 94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 44 08 01 99 didier(a)xemacs.org -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

drv> some reason, ssh doesn't handle my key and asks me for a drv> password. Could this be related to my recent switch to ssh 2 drv> ? APA> Yes, I think so. Try this in your ~/.ssh/config: APA> Host cvs.xemacs.org APA> ForwardAgent no APA> ForwardX11 no APA> Protocol 1 APA> User martinb You should also add: Compression yes CompressionLevel 1 ... to improve throughput. I also highly recommend "fsh" (available via Debian, perhaps elsewhere also) if you are using CVS often and want to eliminate the connection setup time. fsh sets up an ssh connection, and then reuses it for subsequent transactions. It was designed for use with CVS, but also works well for starting X applications on a remote machine via a window manager or toolbar menu, since, when the connection is reused like that, each connection shares the same proxy X server, rather than each getting a separate one.