From: "Eric Martin" <freak4uxxx@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cannot login with publickey on sshd
Date: Thu, 18 Dec 2008 17:59:29 -0500 [thread overview]
Message-ID: <ae47c6e50812181459g3c6be661scd11b49d3a35bd41@mail.gmail.com> (raw)
In-Reply-To: <200812182334.16724.alan.mckinnon@gmail.com>
Great to hear that the problem is solved! I've used puttygen before
to convert keys (both ways) but when I used it the other day to create
a key on windows & convert it wouldn't work. Oh well!
On 12/18/08, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Thursday 18 December 2008 23:17:13 Mick wrote:
>> > The only time I have a problem w/pub/private keys is when
>> > I create them on a windows box and try to export it to ssh. The other
>> > way around always works for me.
>>
>> The MSWindows generated keys will work, either from PuTTY or Cygwin, but
>> you have to be careful with hard returns at the end of lines (CR/LF). Use
>> Notepad++ to paste your key in and you should find that it works fine.
>
> PuTTY comes with a utility to convert it's keys to openssh format. I insist
> my
> PuTTY users do this themselves before they send me the public key to be
> deployed on the servers. It works well for me - if they get stroppy and
> don't
> do this, they don't get access <shrug>
>
> --
> alan dot mckinnon at gmail dot com
>
>
next prev parent reply other threads:[~2008-12-18 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 23:53 [gentoo-user] Cannot login with publickey on sshd Mick
2008-11-29 5:28 ` Eric Martin
2008-11-29 12:27 ` Mick
2008-12-01 4:27 ` Eric Martin
2008-12-01 6:53 ` Mick
2008-12-02 6:35 ` Mick
2008-12-18 13:14 ` Eric Martin
2008-12-18 21:17 ` Mick
2008-12-18 21:34 ` Alan McKinnon
2008-12-18 22:59 ` Eric Martin [this message]
2008-12-19 6:28 ` Mick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae47c6e50812181459g3c6be661scd11b49d3a35bd41@mail.gmail.com \
--to=freak4uxxx@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox