Re: scp problems between Solaris and Tru64
From: Dr. David Kirkby (drkirkby_at_ntlworld.com)
Date: 05/21/03
- Previous message: carloseuv: "Setup Unix tru64"
- In reply to: Casper H.S. ***: "Re: scp problems between Solaris and Tru64"
- Next in thread: gerryt_at_gtconnect.net: "Re: scp problems between Solaris and Tru64"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 21 May 2003 08:30:45 +0100
"Casper H.S. ***" wrote:
> > sparrow % scp -v atlc-4.3.0.tar.gz davek@dobermann:/tmp
> > Executing: program /usr/bin/ssh host dobermann, user davek, command
> > scp -v -t /tmp
> > scp: warning: Executing scp1 compatibility.
> > scp: FATAL: Executing ssh1 in compatibility mode failed (Check that
> > scp1 is in your PATH).
> > lost connection
> I believe this message originates from the remote end.
Yes, I've come to that conclusion too. But is my local Sun requesting
protocol 1 - and if so why? Can I force scp on the Solaris 9 Sun to
try to negotiate only using protocol 2?
This is a summary of the facts about what happens when I attempt to
scp to a remote machine from my Ultra 80 running Solaris 9, with Sun's
ssh tools.
1) When attempting to scp to my own Dec Alpha running Tru64 UNIX,
which had no support for protocol 1, a FATAL ERROR is produced.
2) When attempting to scp to the universities Ultra 1 (running Solaris
8, sshd version 3.1.0 from www.ssh.com, configured to use protocol 1
or 2), the U1 produces a warning message that's its using protocol 1,
but connection occurs.
3) When I try to connect to any of my other 7 local computers (2 PCs
and 5 SPARCstation 20, all running OpenSSH configured for protocol 2
only), no warnings are issued. I'm pretty sure protocol 2 is used in
this case, since only the DSA public keys for my Sun are on these
machines.
These 7 machines run a variety of different operating systems -
Solaris 2.5, Debian (SPARC), Redhat (SPARC), OpenBSD (SPARC), NetBSD
(SPARC), Redhat (Intel) and Solaris 7 (Intel), but all have OpenSSH
3.6p1.
4) The U80 can scp files to itself with no warnings or errors. That's
probably not a very useful thing to do (cp is easier), but it does
work.
This leads me to suspect Sun's scp first attempts protocol 2, but this
fails except when connecting to a computer with OpenSSH. Protocol 1 is
then attempted, which generates a warning or fatal error, depending on
whether the remote machine can accept protocol 1 or not.
I don't know if that makes sense.
-- Dr. David Kirkby, Senior Research Fellow, Department of Medical Physics, University College London, 11-20 Capper St, London, WC1E 6JA. Tel: 020 7679 6408 Fax: 020 7679 6269 Internal telephone: ext 46408 e-mail davek@medphys.ucl.ac.uk
- Previous message: carloseuv: "Setup Unix tru64"
- In reply to: Casper H.S. ***: "Re: scp problems between Solaris and Tru64"
- Next in thread: gerryt_at_gtconnect.net: "Re: scp problems between Solaris and Tru64"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]