From: Rical Jasan <ricaljasan@pacific.net>
To: overseers@sourceware.org
Subject: Re: Updating SSH Key
Date: Mon, 23 Oct 2017 03:56:00 -0000 [thread overview]
Message-ID: <efb44511-fa43-ed5f-13a7-8e6f79dbb5b0@pacific.net> (raw)
In-Reply-To: <m3h8uq8zst.fsf@pepe.airs.com>
On 10/22/2017 05:37 PM, Ian Lance Taylor wrote:
> You can use the "replacekey" command.
> ssh USER@sourceware.org replacekey < NEWKEY
Thank you. Updated just now.
> I don't know if the commands are listed anywhere.
Alright. I tried "listcommands", "list", and "commands", since most of
them seem naturally named (e.g., "How do I replace my key?" ->
replacekey), and only got the hanging login, but it seemed worth a shot.
Rical
next prev parent reply other threads:[~2017-10-23 3:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 8:00 Rical Jasan
2017-10-23 0:37 ` Ian Lance Taylor
2017-10-23 3:56 ` Rical Jasan [this message]
[not found] ` <20171023045747.GA4262@ednor.casa.cgf.cx>
2017-10-23 7:47 ` Rical Jasan
-- strict thread matches above, loose matches on Subject: below --
2006-10-26 20:04 updating SSH key Lee Millward
2006-10-26 20:27 ` Gerald Pfeifer
2006-10-26 21:01 ` Lee Millward
2006-10-30 18:28 ` Lee Millward
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=efb44511-fa43-ed5f-13a7-8e6f79dbb5b0@pacific.net \
--to=ricaljasan@pacific.net \
--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).