From: Ian Lance Taylor <ian@airs.com>
To: "Yangfei \(Felix\)" <felix.yang@huawei.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: Question: how to update ssh public key?
Date: Thu, 23 Jan 2020 05:05:00 -0000 [thread overview]
Message-ID: <m3eevq7ofm.fsf@pepe.airs.com> (raw)
In-Reply-To: <DA41BE1DDCA941489001C7FBD7A8820EE3E05C8A@dggeml527-mbx.china.huawei.com> (Yangfei's message of "Thu, 23 Jan 2020 04:22:42 +0000")
"Yangfei (Felix)" <felix.yang@huawei.com> writes:
> Thanks for the timely reply.
> Yes, I have a backup of the private key in my USB device.
> Does this help in any way?
Yes, that means that you still contact gcc.gnu.org. Using the private
key, you can run
ssh gcc.gnu.org append-key < new-public-key
or you can replace the existing key with
ssh gcc.gnu.org replace-key < new-public-key
You can test whether SSH works with your private key with
ssh gcc.gnu.org alive
Ian
next prev parent reply other threads:[~2020-01-23 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 2:00 Yangfei (Felix)
2020-01-23 3:46 ` Ian Lance Taylor
2020-01-23 4:22 ` Yangfei (Felix)
2020-01-23 5:05 ` Ian Lance Taylor [this message]
2020-01-23 5:27 ` Christopher Faylor
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=m3eevq7ofm.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=felix.yang@huawei.com \
--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).