Re: sftp Authentication Issue (Unix to Windows)

On May 28, 10:55 am, Harry <harryooopot...@xxxxxxxxxxx> wrote:

On May 28, 8:33 am, "steve.burch" <steve.bu...@xxxxxxxxxxx> wrote:

After some assistance from the NT server support guys, it appears that
the public key that I have sent them is in the wrong format (there's a
KnowledgeBase article, ID 31930, posted on the ssh support website
about key incompatibity) - according to one article, the following
command should be run:-

      Now that you have uploaded the public key to the OpenSSH server,
you must convert the public key format from SecSH (the format
generated by the F-Secure SSH client) to OpenSSH (the format supported
by OpenSSH servers). To do this, follow these steps:

      1. On the command line, change to the .ssh directory in your
user account.
      2. Use the following command to convert the key to OpenSSH
format and append the key to the authorized_keys file. Replace with the name of your public key:
      ssh-keygen –i -f >>authorized_keys

My questions on this are:-
1. On which server is this meant to be run - the Unix or Windows?

The term "server" should be in the context of ssh.

From your 1st post, you are running sftp from your Unix box to your
Windows box.

Your sftp on your Unix is a client (in the context of ssh).
Your ssh server on your Windows is an ssh server.

2. It mentions .ssh directory, whereas the Windows server has a .ssh2

.ssh is for ssh1 protocol, while .ssh2 is for ssh2 protocol.

The folder should be on Windows under the %USERPROFILE%
of that particular user.

3. Is there a utility I can run this on the Windows server?

Does your [openssh] Tectia SSH server on your Windows box have an ssh-
keygen.exe ?
If not, get an [openssh] ssh installation from Cygwin onto your


Tectia SSH server should be SSH implementation, rather be
OpenSSH implementation. And Sun's F-Secure should be
OpenSSH implementation.

So, to convert an openssh public key from Sun F-Secure to be used
by Tectia SSH server on Windows, try use Sun's ssh-keygen -x option.
Then transfer the converted public key (in SSH format) to Windows
%USERPROFILE% folder of that particular user.

Someone may correct me if I'm wrong.