From: "Frank Ch. Eigler" <fche@redhat.com>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Mark Wielaard <mark@klomp.org>, Joel Brobecker <brobecker@adacore.com>
Subject: Re: update user brobecke's public SSH key
Date: Thu, 9 Apr 2020 20:31:39 -0400 [thread overview]
Message-ID: <20200410003139.GA18712@redhat.com> (raw)
In-Reply-To: <20200410001040.GD16021@wildebeest.org>
Hi -
> > $ 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
>
> So, if you do actually have bash as shell for your account, then you
> can also edit ~/.ssh/authorized_keys directly.
Exactly.
- FChE
next prev parent reply other threads:[~2020-04-10 0:31 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 [this message]
2020-04-10 12:49 ` Joel Brobecker
-- 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=20200410003139.GA18712@redhat.com \
--to=fche@redhat.com \
--cc=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).