Installation: a shrink-wrap "install everything" from RH9 (CheapBytes CDs). Add ssh 3.2.9 and you have this problem. It may (still) be inept configuration on my part. Also William Hooper is correct; scp (from ssh) is not scp (from OpenSSH) and the two don't talk together nicely. How obvious this isn't reminds me of the ipchains v iptables troubles we saw a while ago. However, a symlink from scp1 to OpenSSH::scp will do the trick. Brian Brunner brian.t.brunner@xxxxxxxxxxxxxxx (610)796-5838 >>> whooper@xxxxxxxxxxxxx 04/03/04 12:06AM >>> joe said: > Brian T. Brunner wrote: > >>Interim: >>/usr/local/bin/scp and /usr/local/bin/scp2 are the same file >>(symlink). >>Making a symlink from /usr/bin/scp to /usr/bin/scp1 cures the failure. >> >>*man* what possessed people to name both utilities scp? >> >> >> > Somebody compiled their own home grown ssh and installed it into > /usr/local? Most likely installed a non-OpenSSH version. > As far as scp1 and scp2, scp1 is just another name for "scp -1 ...", > right? No, and that is where the problem comes in. Not all SSH implimentations support both protocols, some of them have different binaries for SSH v1 and SSH v2. In the case of OpenSSH, making scp1 a link to scp works because the binary supports both protocols. -- William Hooper -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list ******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.hubbell.com - Hubbell Incorporated -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
