sftp Red-Hat client to Windows 2003 Srvr

Steve Lewis — Tue, 15 Aug 2006 08:48:18 GMT

We have a working openssh/sftp connection to a supplier, who has a windows 2003 server, also running an openssh/sftp based server, its fine using password authentication.

The problem is public key authentication.
When I send the id_rsa.pub and id_dsa.pub to the other end and put them into the authorized_keys file, sftp succeeds in authentication, but then drops the connection, which means I cannot do anything. The same happens with ssh.

This is the -vvv output from the client (key ids changed for protection).

debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /home/batch/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 277 lastkey 0x1234567 hint 0
debug2: input_userauth_pk_ok: fp 01:02:03:04:05:06:07:08:09:11:12:13:14:15:16:17
debug3: sign_and_send_pubkey
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: fd 4 setting O_NONBLOCK
debug2: fd 5 is O_NONBLOCK
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: ssh_session2_setup: id 0
debug1: Sending subsystem: sftp
debug1: channel 0: request subsystem
debug2: callback done
debug1: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 131072
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: rcvd eof
debug1: channel 0: output open -> drain
debug1: channel 0: obuf empty
debug1: channel 0: close_write
debug1: channel 0: output drain -> closed
debug1: channel 0: rcvd close
debug1: channel 0: close_read
debug1: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug1: channel 0: almost dead
debug1: channel 0: gc: notify user
debug1: channel 0: gc: user detached
debug1: channel 0: send close
debug1: channel 0: is dead
debug1: channel 0: garbage collecting
debug1: channel_free: channel 0: client-session, nchannels 1
debug3: channel_free: status: The following connections are open:\015
#0 client-session (t4 r0 i3/0 o3/0 fd -1/-1)\015

debug3: channel_close_fds: channel 0: r -1 w -1 e 6
debug1: fd 0 clearing O_NONBLOCK
debug2: fd 1 is not O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 255
Connection closed

It is worth noting that this does work from Linux to HP-UX. I already asked the supplier to change Strictmodes to NO and restart, which is what I needed to get it going here.
Our version Openssh3.6.1.p2, remote version: 3.8.1.p1

Re: sftp Red-Hat client to Windows 2003 Srvr

g33k — Tue, 15 Aug 2006 09:34:12 GMT

http://www.derkeiler.com/Newsgroups/comp.security.ssh/2005-01/0210.html

maybe this is your case... and hopefully also solution

Re: sftp Red-Hat client to Windows 2003 Srvr

Steven E. Protter — Tue, 15 Aug 2006 12:26:43 GMT

Shalom,

I'd think that getting to openssh 3.9 at a minimum might be helpful.

There could be a bug in the Windows openssh server as well. Check for patches and possible upgrades.

SEP

topic Re: sftp Red-Hat client to Windows 2003 Srvr in Operating System - Linux

sftp Red-Hat client to Windows 2003 Srvr

Re: sftp Red-Hat client to Windows 2003 Srvr

Re: sftp Red-Hat client to Windows 2003 Srvr