Re: scp problems between Solaris and Tru64

From: Dr. David Kirkby (drkirkby_at_ntlworld.com)
Date: 05/23/03

  • Next message: sammysammy: "sysstate for Tru64??" 
    Date: Fri, 23 May 2003 11:46:40 +0100

    Nico Kadel-Garcia wrote:
    >
    > gerryt@gtconnect.net wrote:
    > > In article <3ECB2B25.6E4739BB@ntlworld.com>,
    > > "Dr. David Kirkby" <drkirkby@ntlworld.com> writes:
    > >
    > >>"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?
    > >
    > >
    > > Maybe a version issue. Try using ssh instead (which you say does work
    > > in a previous post):
    > >
    >
    > There may also be multiple ssh and sshd daemons installed, along with
    > some potentially odd settings in the config files for the sshd. I'd
    > suspect the sshd operating on the target host is actually not the later
    > installed OpenSSH version. If it's ssh-2.x from ssh.com, then it *will
    > not operate* in ssh1 mode unless the ssh-1.x is pre-installed *before*
    > ssh-2.x compilation. This bit of nastiness is why the OpenSSH with a
    > single dual-protocol client and daemon is so much more supportable.

    This was pretty much a fresh install of Tru64 UNIX. I'd added a couple
    of files to /usr/local and set up a user account, but apart from that,
    there was no other software added, or major configuration changes and
    nothing related to ssh.
     
    > Tell your ssh client to use SSH-2 by saying ssh -o 'Protocol 2'" and see
    > what happens. And you need to make the *client* use protocol 2, not just
    > the server.

    Well, I've given up now on dobermann (the Tru64 UNIX box) and
    installed OpenSSH there, so its a bit late to do some more testing - I
    am not going to go back and re-enable the original ssh stuff on the
    Tru64 box.

    However, the following 4 tests seem to indicate the Sun is quite
    capable of running ssh protocol 2 or scp Protocol 2 and unwilling to
    run protocol 1. (sparrow is the Sun with Solaris 9; dobermann De Alpha
    running Tru64)

    sparrow /export/home/davek % ssh -o 'Protocol 1' dobermann
    Protocol major versions differ: 1 vs. 2

    sparrow /export/home/davek % ssh -o 'Protocol 2' dobermann
    Last login: Fri May 23 11:33:21 BST 2003 from sparrow
    Compaq Tru64 UNIX V5.1B (Rev. 2650); Fri May 2 21:42:35 BST 2003
    $

    sparrow /export/home/davek % scp -o 'Protocol 1' foo
    davek@dobermann:\tmp
    Protocol major versions differ: 1 vs. 2
    lost connection

    sparrow /export/home/davek % scp -o 'Protocol 2' foo
    davek@dobermann:\tmp
    foo 100% |*****************************| 27636
    00:00

    I've made no changes to the Sun, only on Dobermann where I've
    installed OpenSSH. Now things seem to work fine, so I'm leaving well
    alone.

    It's possible I might run into problems on the Tru64 box if I had a
    cluster, as the SSH is a required piece of softare and should not be
    removed. But I don't have a license for the clustering software and
    only one Dec Alpha anyway, so that's not an issue for me. However,
    this issue would perhaps bother someone in a large corporate
    enviroment with a Tru64 cluster. 

    -- 
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
  • Next message: sammysammy: "sysstate for Tru64??"
    • Quantcast