Dear all, I'm currently facing the following situation: My workstation has both ssh2 (.0.13) and ssh1 (.2.27) installed. I would sometimes like to scp files between this computer and a server that is only running ssh1. Now, copying files the other way around (from ssh1 client to ssh2 host) was remedied some time ago after I reported a problem on the server launching the wrong scp; but I'm facing a similar problem the other way around this time. Namely, the "scp" command on my workstation starts scp2. As soon as the ssh connection is established, the v1 server is detected on the other end and ssh2 launches ssh1 instead on the client. However, the scp version is not changed and the result looks like this: $ scp files ... ssh1-host: Executing /usr/local/bin/ssh1 for ssh1 compatibility. command-line line 0: Bad configuration option. Connection lost. $ Obviously, there is a perfectly simple workaround (run scp1 explicitly) but fixing this would be a worthwhile usability enhancement IMHO. -- Atro Tossavainen, email available at URL http colon 2*slash www dot iki dot fi slash atossava slash
