public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: overseers@sourceware.org
Subject: Re: ssh key
Date: Wed, 11 Aug 2004 14:30:00 -0000	[thread overview]
Message-ID: <orsmausxrw.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20040810172805.GA11008@redhat.com>

On Aug 10, 2004, "Frank Ch. Eigler" <fche@redhat.com> wrote:

> Hi -
> On Tue, Aug 10, 2004 at 02:14:16PM -0300, Alexandre Oliva wrote:
>> [...]  I'm just thinking it might be reasonable to have, as
>> part of the sign-up procedure, a gpg pubkey registration, and demand
>> such requests to be signed with the corresponding privkey.

> But how would that solve the typical problem that appears here, which
> is that people lose their old ssh private keys (due to change of hardware
> or fatfingering rm or whatever)?  Files in $HOME/.gnupg are not much more
> likely to survive than $HOME/.ssh.

Well...  You're supposed to keep the GPG key revocation certificate in
permanent storage, and you might as well have the GPG private key
itself saved somewhere.  Sure it's not bullet-proof, and we may have
to handle exceptions, but those would not be the rule.

In this one case, it was not about a lost key, it was about requesting
an additional key.

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

  reply	other threads:[~2004-08-10 17:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07 16:55 James A. Morrison
2004-08-09  7:38 ` Christopher Faylor
2004-08-09 14:33   ` Alexandre Oliva
2004-08-09 20:01     ` Christopher Faylor
2004-08-10 17:28       ` Alexandre Oliva
2004-08-10 17:34         ` Frank Ch. Eigler
2004-08-11 14:30           ` Alexandre Oliva [this message]
2008-06-23 20:57 Janus Weil
2008-06-24 11:57 ` Jonathan Larmour
2018-10-16 22:12 SSH key David Miller
2018-10-16 22:41 ` Ian Lance Taylor
2018-10-16 23:18   ` David Miller
2018-10-16 23:25     ` David Miller
2018-10-16 22:44 ` Frank Ch. Eigler

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=orsmausxrw.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=fche@redhat.com \
    --cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).