Date: Thu, 23 May 2002 10:30:04 -0700 (PDT) From: Alan Larson <larson@eng.paix.net> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/34850: scp cannot talk to ssh2 sites that have Ssh1Compatability no Message-ID: <200205231730.g4NHU4j61566@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/34850; it has been noted by GNATS. From: Alan Larson <larson@eng.paix.net> To: freebsd-gnats-submit@FreeBSD.org, larson@paix.net Cc: Subject: Re: misc/34850: scp cannot talk to ssh2 sites that have Ssh1Compatability no Date: Thu, 23 May 2002 10:24:20 -0700 (PDT) Restatement of the problem: When a client is talking to sshd2 from openssh, scp will likely fail. This is because sshd2 will notice flags that indicate the transfer is in scp1 protocol, and will attempt to invoke scp1 via compatability. (This is somewhat similar to the invoking of sshd1 if that has not been disabled.) Unfortunately, the path in effect at the time is: /usr/bin /bin /usr/local/ssh2/bin which doesn't contain the scp1 program or link, (presuming an installation of ssh2 in /usr/local). This is a problem for any client that speaks ssh2 link and authentication, but speaks scp1 for file copies. openssh will do this. A test for this is: ssh -x host.foo.com 'echo $path;scp -p -f .cshrc' < /dev/zero which will echo the path it tried. The fix (done on the server system running sshd2) is: test -e /usr/local/ssh2/bin/scp1 || \ ln -s ../../ssh/bin/scp1 /usr/local/ssh2/bin/scp1 I have installed this fix on our systems, and it solved the problem. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205231730.g4NHU4j61566>