From: Christopher Faylor <cgf@alum.bu.edu>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@sources.redhat.com
Subject: Re: Error trying to get CVS write access via web-form
Date: Fri, 02 Apr 2004 19:16:00 -0000 [thread overview]
Message-ID: <20040402191616.GA8205@coc.bosbc.com> (raw)
In-Reply-To: <20040402181529.GM26117@redhat.com>
On Fri, Apr 02, 2004 at 01:15:30PM -0500, Frank Ch. Eigler wrote:
>>[...]
>>Is there a way to get ssh to tell us if the key looks right? That's
>>probably the best way to verify keys. [...]
>
>Or an even tougher-love approach would be to force new account holders
>to log in using the putative key within some time limit after initial
>account activation, to prove they hold a matching private key.
Yeah, a secondary verification step might be nice.
"ssh-keygen -l" does seem to do the job. The only challenge is the
necessity of creating a temp file. I hate that. I tried using the
standard work around of passing the key file in a pipe and using
/proc/self/fd/0 but ssh-keygen is way too clever to allow that.
Anyway, now it's back to real work for me. I'll look at this more
tonight.
cgf
next prev parent reply other threads:[~2004-04-02 19:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 12:37 Ranjit Mathew
2004-04-02 15:57 ` Christopher Faylor
2004-04-02 16:17 ` Frank Ch. Eigler
2004-04-02 16:41 ` Christopher Faylor
2004-04-02 16:45 ` Frank Ch. Eigler
2004-04-02 16:57 ` Christopher Faylor
2004-04-02 17:08 ` Frank Ch. Eigler
2004-04-02 17:23 ` Christopher Faylor
2004-04-02 17:29 ` Frank Ch. Eigler
2004-04-02 17:40 ` Christopher Faylor
2004-04-02 18:06 ` Christopher Faylor
2004-04-02 18:15 ` Frank Ch. Eigler
2004-04-02 19:16 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-01 6:59 Ranjit Mathew
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=20040402191616.GA8205@coc.bosbc.com \
--to=cgf@alum.bu.edu \
--cc=fche@redhat.com \
--cc=overseers@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).