sftp from HP-UX to Windows

[John Kittel]

HP-UX 11.11, SSH A.04.20.004.

Windows 2000, Ipswitch Inc. WS_FTP server V5.

Having trouble establishing a connection from HP-UX to Windows. I can connect and transfer files between HP-UX systems. Also, Windows systems can connect and transfer files between themselves.

The Windows admin here installed, setup, configured the Windows side. He says either the product doesn't support sftp with SSH, or it's broken, - so he has it set up to do sftp over SSL.

Do you think it is possible to use HP-UX sftp to work with this Windows "sftp over SSL" ?

Also, between my HP-UX systems, I generated a key on sender, and copied the public key to
authorized_keys file in .ssh directory for account on remote host. But Windows admin says no such thing should be needed for sftp ( with ssl) to this Windows host.


With my current config / setup, - here is output of connect attempt from hp-ux to Windows with LogLevel=DEBUG3

#sftp -oPort=27 -oLogLevel=DEBUG3 user@w2ksrv
Connecting to w2ksrv...
debug1: Reading configuration data /opt/ssh/etc/ssh_config
debug3: Seeding PRNG from /opt/ssh/libexec/ssh-rand-helper
debug2: ssh_connect: needpriv 0
debug1: Connecting to w2ksrv [10.1.0.10] port 27.
debug1: Connection established.
debug1: permanently_set_uid: 0/3
debug1: identity file /root/.ssh/id_rsa type -1
debug3: Not a RSA1 key file /root/.ssh/id_dsa.
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type '-----END'
debug3: key_read: missing keytype
debug1: identity file /root/.ssh/id_dsa type 2
debug1: ssh_exchange_identification: 220-sftp.mydomain.com X2 WS_FTP Server 5.0
.4 (87049245)


debug1: ssh_exchange_identification: 220-This Is A Secure FTP Site


debug1: ssh_exchange_identification: 220-If you do not have account on this site
,


debug1: ssh_exchange_identification: 220-please disconnect now.


debug1: ssh_exchange_identification: 220 sftp.mydomain.com X2 WS_FTP Server 5.0
.4 (87049245)


debug1: ssh_exchange_identification: 500 connection timed out


ssh_exchange_identification: Connection closed by remote host
Connection closed

[TwoProc]

John, I've gotten it to work just fine with the "putty" tools for Windows using the keys, but that was going from Windows to Unix.

Do go the other way (Unix to Windows), I've not done it before, but I'd recommend trying first with Cygwin, it's free!

[Steven E. Protter]

Shalom,

You need an openssh/sftp server for windows.

http://www.networksimplicity.com

Can't beat the price.

SEP

[Bill Hassell]

The problem is not with Windows but with the 3rd party product. You'll have to contact the vendor for help. It seems that there are a lot of SSH products but OpenSSH compatibility does not seem to be a product feature. The errors indicate problems resolving public keys.

[John Kittel]

For years I've been unsuccessfully advocating that our Windows people get /try openSSH for Windows. I guess I will give that another try.

Thanks for the help.

- John

[Logu_2]

You can use cygwin-openssh server on windows and can use sftp from hpux to windows.

There are some more sftp servers available for windows you can also try out one.

-logu

[Mike Keighley · Accepted solution]

> Do you think it is possible to use HP-UX
> sftp to work with this Windows "sftp over
> SSL" ?

Alas no, they are quite different protocols, although their aim is the same (encrypted ftp).

sftp uses port 22, same as ssh or scp.

ftp-over-ssl uses the usual ftp ports 20 and 21 and adds extensions to the ftp protocol to allow encryption of the control channel, or of both control and data.

I find this page very useful:
http://www.ford-hutchinson.com/~fh-1-pfh/ftps-ext.html

First off it explains the 3 ftp-over-ssl variants and tries to explain why ftp/tls is the "best" one.

Then there is a summary of client and server software, both free and commercial, with an occasional note when a product supports ssh/sftp as well.

I suggest beating on your windows admin with this list, until he agrees to install what you asked for in the first place: an sftp server !

[John Kittel]

Not sure what we are going to do yet... But at least I now better understand the issues / confusion over sftp, ftps, SSH, SSL, etc.

- John