scp oddities on 5.1B

From: Eric Zylstra (ezylstra@ucla.edu)
Date: Wed Feb 26 2003 - 18:23:32 EST


I recently upgraded two machines to Tru64 5.1B. After the upgrade, I
installed OpenSSH 3.5p1 as my preference in the ssh world is for
OpenSSH. To be sure my version of the daemon ran instead of the 5.1B
default, I mved '/sbin/rc3.d/S34sshd' to '/sbin/rc3.d/K34sshd' and
inserted openssh into the '/etc/inet.local' file. I double checked
'/etc/inetd.conf' to verify there was no ssh service managed by inetd.
I double checked to be sure all running sshd processes were my OpenSSH,
'/usr/local/sbin/sshd'. Many reboots have transpired since then.
sshing and sftping between the two works fine.

Trying to scp between the two machines results in:
    scp: warning: Executing scp1.
    scp: FATAL: Executing ssh1 in compatibility mode failed (Check that
scp1 is in your PATH).

It appears to me the SSH (not OpenSSH) version of the sshd is handling
the interaction (no ssh2 daemon running, should not be possible). I'm
not running the ssh2 daemon but the OpenSSH daemon. I checked another
time to verify this (and again, and again, and again). Check another
way: `which sshd` = '/usr/local/sbin/sshd'. `grep ssh
/usr/inetd.conf` = "".

I am using the OpenSSH scp client (explicitly calling
`/usr/local/bin/scp`). The PATHs on both machines begin with
'/usr/local/sbin:/usr/local/bin' as the first directory.

The only thing that has fixed one machine is to delete everything to do
with the SSH version (/etc/ssh2, /usr/ssh, /usr/bin/ssh*,
/usr/sbin/ssh*). I'm not changing the other machine until I can figure
out what is happening.

Eric Zylstra
ezylstra@ucla.edu



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:09 EDT