SUMMARY: scp problems

From: Darryl Cook (dlc_at_cs.appstate.edu)
Date: 10/08/03

  • Next message: Christian Wessely: "SUMMARY: reset alarm in Raidshelf?"
    Date: Wed, 08 Oct 2003 08:37:30 -0400
    To: Tru64 Mailing List <tru64-unix-managers@ornl.gov>, ssh <secureshell@securityfocus.com>
    
    

    Thanks to all those who offered suggestions.....ultimately I tracked
    down the problem with the help of a local networking associate Oscar
    Knight. The problem was that a gcc library was missing. I happened to
    walk by the console and there on the console messages was a message
    stating a problem with scp and a missing library. So i went looking
    for the library and lo and behold it was in the src area but not in the
    /usr/local/lib area. Once I reinstalled it everything began working
    fine again.

    thanks!
    darryl

    Darryl Cook wrote:

    > I recently upgraded openssh to 3.7.1p2 and lost scp capability. I am
    > able to ssh in using protocol 2 just fine but when I run scp it
    > attempts to make a connection and then gives me the message <lost
    > connection> and drops me out without transferring the files.
    >
    > I have run both sshd and scp in debug mode and everything looks fine.
    > I looked at the log files and it says I was authenticicated fine. Ive
    > tried using key and forcing it to ask me for a password and get the
    > same result. Im running Tru64 versions 5.1b and a second machine
    > runs 4.0f, both get the same results. Below is the output from a
    > run.....
    >
    > Executing: program /usr/local/bin/ssh host sc.cs, user (unspecified),
    > command scp -v -t /u/csd/dlc/temp
    > OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.7b 10 Apr 2003
    > debug1: Reading configuration data /usr/local/etc/ssh_config
    >
    > debug1: Connecting to sc.cs [152.10.143.14] port 22.
    >
    > debug1: Connection established.
    >
    > debug1: identity file /u/csd/dlc/.ssh/identity type -1
    >
    > debug1: identity file /u/csd/dlc/.ssh/id_dsa type -1
    >
    > debug1: identity file /u/csd/dlc/.ssh/id_rsa type 1
    >
    > debug1: Remote protocol version 1.99, remote software version
    > OpenSSH_3.7.1p2
    >
    > debug1: match: OpenSSH_3.7.1p2 pat OpenSSH*
    >
    > debug1: Enabling compatibility mode for protocol 2.0
    >
    > debug1: Local version string SSH-2.0-OpenSSH_3.7.1p2
    >
    > debug1: SSH2_MSG_KEXINIT sent
    >
    > debug1: SSH2_MSG_KEXINIT received
    >
    > debug1: kex: server->client aes128-cbc hmac-md5 none
    >
    > debug1: kex: client->server aes128-cbc hmac-md5 none
    >
    > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
    >
    > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    >
    > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    >
    > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    >
    > debug1: Host 'sc.cs' is known and matches the RSA host key.
    >
    > debug1: Found key in /u/csd/dlc/.ssh/known_hosts:32
    >
    > debug1: ssh_rsa_verify: signature correct
    >
    > debug1: SSH2_MSG_NEWKEYS sent
    >
    > debug1: expecting SSH2_MSG_NEWKEYS
    >
    > debug1: SSH2_MSG_NEWKEYS received
    >
    > debug1: SSH2_MSG_SERVICE_REQUEST sent
    >
    > debug1: SSH2_MSG_SERVICE_ACCEPT received
    >
    > debug1: Authentications that can continue: publickey,password,hostbased
    >
    > debug1: Next authentication method: publickey
    >
    > debug1: Trying private key: /u/csd/dlc/.ssh/identity
    >
    > debug1: Trying private key: /u/csd/dlc/.ssh/id_dsa
    >
    > debug1: Offering public key: /u/csd/dlc/.ssh/id_rsa
    >
    > debug1: Server accepts key: pkalg ssh-rsa blen 149
    >
    > debug1: read PEM private key done: type RSA
    >
    > debug1: Authentication succeeded (publickey).
    >
    > debug1: channel 0: new [client-session]
    >
    > debug1: Entering interactive session.
    >
    > debug1: Sending command: scp -v -t /u/csd/dlc/temp
    >
    > debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
    >
    > debug1: channel 0: free: client-session, nchannels 1
    >
    > debug1: fd 0 clearing O_NONBLOCK
    >
    > debug1: fd 1 clearing O_NONBLOCK
    >
    > debug1: fd 2 clearing O_NONBLOCK
    >
    > debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.4 seconds
    >
    > debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
    >
    > debug1: Exit status 1
    >
    > lost connection
    >
    >
    > any help appreciated,
    >
    > darryl
    >


  • Next message: Christian Wessely: "SUMMARY: reset alarm in Raidshelf?"

    Relevant Pages

    • SUMMARY: scp problems
      ... stating a problem with scp and a missing library. ... Darryl Cook wrote: ... > connection> and drops me out without transferring the files. ... > debug1: Entering interactive session. ...
      (SSH)
    • scp fails - excepted on very small files
      ... When trying to scp or sftp some files, from machine A to machine B, I can get ... the connection created but the file doesn't transfer. ... debug1: Reading configuration data /home1/gnurou/.ssh/config ... Rhosts Authentication disabled, originating port will not be trusted. ...
      (SSH)
    • scp problem
      ... I recently upgraded openssh to 3.7.1p2 and lost scp capability. ... able to ssh in using protocol 2 just fine but when I run scp it attempts ... to make a connection and then gives me the message and ... debug1: Connecting to sc.cs port 22. ...
      (SSH)
    • scp problems
      ... I recently upgraded openssh to 3.7.1p2 and lost scp capability. ... able to ssh in using protocol 2 just fine but when I run scp it attempts ... to make a connection and then gives me the message and ... debug1: Connecting to sc.cs port 22. ...
      (Tru64-UNIX-Managers)
    • Re: xterm binary ascii transfer
      ... there's not much point in securing the network. ... Okay, if you don't like my answer, there are more reasons why scp is ... Over a TCP/IP connection, ...
      (comp.os.linux)