public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Overseers mailing list <overseers@sourceware.org>
Subject: Re: update user brobecke's public SSH key
Date: Fri, 10 Apr 2020 05:49:38 -0700	[thread overview]
Message-ID: <20200410124938.GM9860@adacore.com> (raw)
In-Reply-To: <20200410001040.GD16021@wildebeest.org>

> > Thanks Mark. Unfortunately, these don't work:
> > 
> >     $ ssh sourceware.org replacekey < .ssh/id_rsa.pub
> >     bash: replacekey: command not found
> >     $ ssh sourceware.org appendkey < .ssh/id_rsa.pub
> >     bash: appendkey: command not found
> 
> That is odd. The user brobecke shouldn't have a bash shell.  Could it
> be that ssh is using another account for which you have a real shell?
> Could you try the above with an explicit brobecke@sourceware.org ?

Headslap. I'm an idiot...

Thanks a lot for pointing me in the right direction, Mark. For
sourceware.org, because I have access to two accounts ("brobecke"
is my restricted user account for pushing commits, while "gdbadmin"
is a shared account for GDB admin stuff, and in particular for
releases). Because I was doing "ssh gdbadmin@sourceware" a lot,
I thought it would be more efficient to configure my SSH to
use gdbadmin by default when ssh-ing to sourceware, and then
force "brobecke" back in my git repositories. That works very
well until the day you miss the implication on the instructions
above.

I'm happy to confirm that...

    $ ssh brobecke@sourceware.org replacekey < .ssh/id_rsa.pub

... worked like a charm. From there, I removed the old key from
my agent, and was able to fetch from GDB, so I think it's all set.

Thanks again!

-- 
Joel

  parent reply	other threads:[~2020-04-10 12:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 22:53 Joel Brobecker
2020-04-09 23:09 ` Mark Wielaard
2020-04-09 23:21   ` Joel Brobecker
2020-04-10  0:10     ` Mark Wielaard
2020-04-10  0:31       ` Frank Ch. Eigler
2020-04-10 12:49       ` Joel Brobecker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-09 20:08 Joel Brobecker

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=20200410124938.GM9860@adacore.com \
    --to=brobecker@adacore.com \
    --cc=mark@klomp.org \
    --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).