On Fri, 27 Jun 2003 05:12 am, [EMAIL PROTECTED] wrote: > is one of these server running ssh.com and the other openssh? Will you > paste the results of your scp attempt in verbose mode to the next email? > (use the -v swith for verbose mode) > thanks-
No, both ends are running OpenSSH, although the client end is v3.1 and the server is v3.6 I have re-emerged openssh on the server, with the optimization flag removed from CFLAGS. The resulting CFLAGS is: CFLAGS="-mcpu=athlon-mp -pipe" $ scp -v xx [EMAIL PROTECTED]:/home/paulcol Executing: program /usr/bin/ssh host dropbear.no-ip.com, user paulcol, command scp -v -t /home/paulcol OpenSSH_3.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 1001 geteuid 0 anon 1 debug1: Connecting to dropbear.no-ip.com [203.45.117.254] port 22. debug1: temporarily_use_uid: 1001/1001 (e=0) debug1: restore_uid debug1: temporarily_use_uid: 1001/1001 (e=0) debug1: restore_uid debug1: Connection established. debug1: read PEM private key done: type DSA debug1: read PEM private key done: type RSA debug1: identity file /home/paulcol/.ssh/identity type -1 debug1: identity file /home/paulcol/.ssh/id_rsa type -1 debug1: identity file /home/paulcol/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p2 debug1: match: OpenSSH_3.6.1p2 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.1p1 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: dh_gen_key: priv key bits set: 132/256 debug1: bits set: 1602/3191 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'dropbear.no-ip.com' is known and matches the RSA host key. debug1: Found key in /home/paulcol/.ssh/known_hosts:1 debug1: bits set: 1659/3191 debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password,keyboard-interactive debug1: next auth method to try is publickey debug1: try privkey: /home/paulcol/.ssh/identity debug1: try privkey: /home/paulcol/.ssh/id_rsa debug1: try privkey: /home/paulcol/.ssh/id_dsa debug1: next auth method to try is keyboard-interactive debug1: authentications that can continue: publickey,password,keyboard-interactive debug1: next auth method to try is password [EMAIL PROTECTED]'s password: debug1: packet_send2: adding 64 (len 60 padlen 4 extra_pad 64) debug1: ssh-userauth2 successful: method password debug1: fd 4 setting O_NONBLOCK debug1: fd 5 setting O_NONBLOCK debug1: channel 0: new [client-session] debug1: send channel open 0 debug1: Entering interactive session. debug1: ssh_session2_setup: id 0 debug1: Sending command: scp -v -t /home/paulcol debug1: channel request 0: exec debug1: channel 0: open confirm rwindow 0 rmax 32768 [the output sat here until I hit ^c, then continued with the following lines] debug1: channel_free: channel 0: client-session, nchannels 1 debug1: fd 0 clearing O_NONBLOCK debug1: fd 1 clearing O_NONBLOCK Killed by signal 2. debug1: Calling cleanup 0x80583c0(0x0) debug1: Calling cleanup 0x80634c0(0x0) > -----Original Message----- > From: Paul Colquhoun [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 25, 2003 4:12 PM > To: [EMAIL PROTECTED] > Subject: Re: [gentoo-user] Problem with scp > > > On Thu, 26 Jun 2003 01:31 am, [EMAIL PROTECTED] wrote: > > I have run into certain issues with scp, where the remote server will > only > > accept "scp -v -2 [EMAIL PROTECTED] connections, because the remote server is > > forcing protocol 2 only connections. Have you tried that? > > > I tried "scp -oProtocol=1" and "scp -oProtocol=2", neither made any > difference. -- Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/~paulcol Asking for technical help in newsgroups? Read this first: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- [EMAIL PROTECTED] mailing list
