From owner-freebsd-bugs Thu May 23 10:30:15 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B81E837B405 for ; Thu, 23 May 2002 10:30:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g4NHU4j61566; Thu, 23 May 2002 10:30:04 -0700 (PDT) (envelope-from gnats) Date: Thu, 23 May 2002 10:30:04 -0700 (PDT) Message-Id: <200205231730.g4NHU4j61566@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Alan Larson Subject: Re: misc/34850: scp cannot talk to ssh2 sites that have Ssh1Compatability no Reply-To: Alan Larson Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/34850; it has been noted by GNATS. From: Alan Larson 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