Topic: confused about ssh options

[robert]

There most certainly is SSH2 support in e-smith. I've used MacSSH and SSH-Winclient with SME's ssh server and both are SSH2-only clients.
I'm not quite sure what exactly you've been trying to do, but from the look of it it's certainly different from what I did to set up public key authentication with ssh and which I've described with step-by-step instructions above. If you find these instructions unclear, please have a look at some of the other documentation available on this and other sites, which I'm sure will be very similar.
Actually, I'll just send you an email off-list.

[Isaac]

robert wrote:
>
> There most certainly is SSH2 support in e-smith. I've used
> MacSSH and SSH-Winclient with SME's ssh server and both are
> SSH2-only clients.

I've got it working with SSH2 too. It must be the way PuTTY generates a public SSH2 key. Because when i import a private OpenSSH key in Putty it is converted as a usable Private SSH2 PuTTY key. But when I paste the Putty public SSH2 string in authorized_keys the PuttY private key is refused.

I also noticed that a public rsa key generated with ssh_keygen ends with the username under which the key is generated eg isaac@blabla. This is not the case with puttygen (as it does not know the username).

Isaac

[robert]

Isaac wrote:
>
> robert wrote:
> >
> > There most certainly is SSH2 support in e-smith. I've used
> > MacSSH and SSH-Winclient with SME's ssh server and both are
> > SSH2-only clients.
>
> I've got it working with SSH2 too. It must be the way PuTTY
> generates a public SSH2 key. Because when i import a private
> OpenSSH key in Putty it is converted as a usable Private SSH2
> PuTTY key. But when I paste the Putty public SSH2 string in
> authorized_keys the PuttY private key is refused.
>
Which is why I keep telling you that you should use the -i switch for ssh-keygen to _i_mport PuTTY's public key into authorized_keys in a format that the ssh-server likes.
You did things the other way around. You generated the keys on the server, then copied the private key to your client. I believe the most common practice is to always leave the private key on the host that generated it and to only distribute the public key (which is not secret) to other hosts. But hey, it's a free country, you can do whatever you like.

> I also noticed that a public rsa key generated with
> ssh_keygen ends with the username under which the key is
> generated eg isaac@blabla. This is not the case with puttygen
> (as it does not know the username).
>
> Isaac