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 0DB5A385841B for ; Tue, 22 Feb 2022 12:27:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 0DB5A385841B Received: from reform (deer0x16.wildebeest.org [172.31.17.152]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id E433830008AE; Tue, 22 Feb 2022 13:27:56 +0100 (CET) Received: by reform (Postfix, from userid 1000) id 9C79D2E813D1; Tue, 22 Feb 2022 13:27:56 +0100 (CET) Date: Tue, 22 Feb 2022 13:27:56 +0100 From: mark To: Overseers mailing list Cc: Xionghu Luo Subject: Re: Request from Xionghu Luo Message-ID: References: <20220218042054.5B5CA3858001@sourceware.org> <20220218052100.GA22670@cgf.cx> <990b65f.27f4.17f0b72259d.Coremail.yingyuefengyi@163.com> <968fa88.19e6.17f1d2e32f6.Coremail.yingyuefengyi@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <968fa88.19e6.17f1d2e32f6.Coremail.yingyuefengyi@163.com> X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE 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: Tue, 22 Feb 2022 12:27:59 -0000 Hi, On Tue, Feb 22, 2022 at 12:47:21AM +0800, Xionghu Luo via Overseers wrote: > Ping? > > thanks, i leaved IBM to another company, so I don't have access to > the machine lep824e1v.canlab.ibm.com any more, how to handle such > kind of circumstance, please? Is there a way to show you are the same person that controlled the previous ssh key for this account? If so you can provide us with a new ssh pub key to install. Please make sure you understand how to keep your ssh key secure and take measures to not loose it again. Note that ssh keys are not tied to specific machines. Thanks, Mark