From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 4D5073858D35 for ; Mon, 11 Oct 2021 11:48:47 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 4D5073858D35 Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id E04243000711; Mon, 11 Oct 2021 13:48:44 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id E8C70413CEBD; Mon, 11 Oct 2021 13:48:43 +0200 (CEST) Message-ID: <75f74ece3ca9dcdb30030a402720837367df2b2e.camel@klomp.org> Subject: Re: ssh keys From: Mark Wielaard To: Overseers mailing list , overseers@gcc.gnu.org Cc: Eric Gallager Date: Mon, 11 Oct 2021 13:48:43 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2021 11:48:48 -0000 Hi, Eric, On Sun, 2021-10-10 at 21:46 -0400, Eric Gallager via Overseers wrote: > Hello GCC Overseers, it's Eric Gallager here, and I'd like to get > back > to committing to the GCC project again. The last time I committed was > back in the SVN days, and it was from a different computer than I > currently use, and I'm afraid my ssh keys from the old computer got > lost in the migration process somehow, so if I'm going to get back to > committing again, I'm going to need to be able to use a new ssh key > (since I haven't been able to find my old one). > [...] > Let me know if there are any other ways I can verify my identity in > order to get my ssh keys switched, and I apologize for my > scatterbrainedness in letting this situation arise. Please sent the ssh pubkey (the ~/.ssh/id_*.pub you are actually using) and we'll install it for you if you promise to take good care of the private part. Cheers, Mark