[Toolserver-l] Putty key problems

[tools.20.connelm at spamgourmet.com]

> Message: 2
> Date: Mon, 18 Jun 2007 11:58:58 +0200
> From: toolserver-l.wikipedia.org at publi.purodha.net
> Subject: [Toolserver-l] Key poblem logging in with putty
> To: toolserver-l at lists.wikimedia.org
> Message-ID: <109213064793.20070618115858 at purodha.net>
> Content-Type: text/plain; charset=us-ascii
>
> I am usually using secureCRT - http://vandyke.com/ - to
> log in to the toolserver.
>
> putty refuses secureCRTs key file ("this is not a key file")
> which is the only one I have.
>
> Can I convert the key file, which was generated by openssh,
> to a format that makes putty happy?
> If so, how do I do that, or where to find appropriate infos?
>
> Or should I rather generate a different key pair for putty?
> How would that be done, and how to implemet it, without
> superseeding the one already in use with secureCRT?
>
> Thank you for your help!
>
> Purodha
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Toolserver-l mailing list
> Toolserver-l at lists.wikimedia.org
> http://lists.wikimedia.org/mailman/listinfo/toolserver-l
>
>
> End of Toolserver-l Digest, Vol 20, Issue 9
> *******************************************
>


Yes, PuTTY can import "regular" SSH keys.  Run "puttygen.exe" then
"Conversions" --> "Import"...

Yes, you can alternately use puttygen.exe to generate (and export) fresh
keys then use SecureCRT to add them to ~/.ssh/authorized_keys

Remember to save your putty settings before connecting.  Remember to use
SSH2.  Remember to fiddle with "Window" --> "Translation" to get UTF-8.

If I recall correctly, you still can't save "default settings" but if you
give the connection a name (e.g. "toolserver") before saving, they persist.

Connel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.wikimedia.org/pipermail/toolserver-l/attachments/20070618/b2e3da85/attachment.htm