public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@gcc.gnu.org, Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Subject: Re: new ssh key
Date: Thu, 05 Jun 2008 03:56:00 -0000	[thread overview]
Message-ID: <20080602194034.GA9500@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20080602191917.GB3827@ins.uni-bonn.de>

On Mon, Jun 02, 2008 at 09:19:18PM +0200, Ralf Wildenhues wrote:
>Hello Christopher,
>
>* Christopher Faylor wrote on Mon, Jun 02, 2008 at 08:17:08PM CEST:
>> On Mon, Jun 02, 2008 at 07:57:06PM +0200, Ralf Wildenhues wrote:
>> >Hello overseers,
>> >
>> >please drop my old SSH key in the digital waste bin, and install the
>> >attached one instead, for access to sources.redhat.com.
>> 
>> Can you use the 'replacekey' functionalty of your account?
>> 
>> ssh sourceware.org 'replacekey' < newkey.pub
>
>That did not work:
>$ ssh rwild@sourceware.org replacekey < id_rsa.pub
>bash: replacekey: command not found
>
>However, I did not know until now that I can just interactively log in
>to sourceware.org and replace the key in .ssh/authorized_keys myself.
>I've done that now, and things seem to work fine.

Hmm.  If you didn't know that you could interactively login that would imply
that you probably don't need login privileges.  Maybe you slipped through the
cracks when we tightened this up.

Unless I hear otherwise from you I'll be changing your privileges to source
control access only.  Once that happens then the "replacekey" and "appendkey"
commands will work.

cgf

  reply	other threads:[~2008-06-02 19:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 19:20 Ralf Wildenhues
2008-06-02 19:41 ` Christopher Faylor
2008-06-02 20:00   ` Ralf Wildenhues
2008-06-05  3:56     ` Christopher Faylor [this message]
2008-06-06 15:22       ` Ralf Wildenhues
  -- strict thread matches above, loose matches on Subject: below --
2020-06-20 17:39 New SSH key Marc Glisse
2020-06-20 20:03 ` Christopher Faylor
2020-06-20 20:36   ` Marc Glisse
2017-09-03 12:46 New ssh key Anthony Green
2017-09-03 13:07 ` Frank Ch. Eigler
2017-05-21 15:00 new " Thomas Koenig
2017-02-22 20:37 David Teigland
2017-02-22 20:41 ` Frank Ch. Eigler
2016-02-04  9:21 New SSH key Simon Dardis
2016-02-04 16:57 ` Ian Lance Taylor
2016-02-04 17:01   ` Simon Dardis
2016-02-05  4:45     ` Ian Lance Taylor
2016-01-12 23:13 new " Ben Elliston
2016-01-13  1:47 ` Ian Lance Taylor
2015-12-04  8:50 new ssh key Richard Henderson
2015-12-04  8:57 ` Ian Lance Taylor
2008-05-19 22:00 Thiago Jung Bauermann
2008-05-20  0:36 ` Jonathan Larmour
2007-06-22 13:56 Jonathan Brassow
2004-10-15 16:52 New SSH key David Gilbert
2004-10-16  1:13 ` Frank Ch. Eigler
2000-12-30  6:08 Jesper Skov
2000-06-16  2:42 ` Jesper Skov
2000-12-30  6:08 ` Jeffrey A Law
2000-06-16  7:16   ` Jeffrey A Law

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=20080602194034.GA9500@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=overseers@gcc.gnu.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).