key exchange from Unix to Windows 2003 Tectia SSH server

[Ratzie]

Has anyone been successful with Key exchanges from the HP unix server (client) to a windows 2003 Tectia ssh server.


On HP Unix client, I have converted my pub key to tectia format.
ssh-keygen -e -f id_dsa.pub > lhradowy_ssh2.pub

I then sftp to Windows 2003 server (the tectia ssh server) and placed in:
C:\Documents and Settings\lhradowy\.ssh2\authorized_keys directory

We are using the default ssh-server-config-default.xml which does allow for public authentication methods.

Where are we going wrong.
Should be fairly easy...

[Steven E. Protter]

Shalom,

I've done it with the http://www.networksimplicity.com and the putty client on windows.

I always made sure I did it root to root, root on Unix, created a root admin user in Windows.

Its not my idea of fun.

SEP

[Ratzie]

We have tried to get the cygwin product to work as well. But to allow, sftp or scp with multiple user ids from Unix clients to upload a file to Windows 2003 server with out passwds, or using public key authentication has not worked either. So this is why we want to try Tectia, with an ACTUAL Windows SSH server product.

[Bill Hassell]

You'll need a support contract from SSH Communications Security, but I would ask them about the issues. You'll need a -ddd log of the client session for tech support to examine. Since it is a commercial product, they will have a fairly strong interest in resolving the issue. Hopefully, they won't ask you to purchase their Unix SSH client :-(

One of the areas where public keys seem to incur errors is adding them to the server's files. They must be plain ASCII so only Notepad should be used and any ftp/sftp transfer must convert formats using the ASCII command. Extra blank lines or special characters may interfere with the server's public key handling.

[Ratzie]

Scrapped OpenSSH for Windows, scrapped Tectia, and went with WinSSHD by BitVise. Had it up and running in 20 minutes!