From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cgf.cx (external.cgf.cx [107.170.62.102]) by sourceware.org (Postfix) with ESMTP id 1C467393FC32 for ; Tue, 17 Mar 2020 03:13:22 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx D86644066A X-Spam-Level: X-Spam-CGF-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.3 spammy=alive, 2.5, H*r:unknown, H*M:cgf Received: from ednor.cgf.cx (unknown [100.0.105.127]) by cgf.cx (Postfix) with ESMTPA for ; Mon, 16 Mar 2020 23:13:20 -0400 (EDT) Received: by ednor.cgf.cx (sSMTP sendmail emulation); Mon, 16 Mar 2020 23:13:19 -0400 Date: Mon, 16 Mar 2020 23:13:19 -0400 From: Christopher Faylor To: Overseers mailing list Subject: Re: problems with ssh keys Message-ID: <20200317031318.GA977@cgf.cx> Mail-Followup-To: Overseers mailing list References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-96.9 required=5.0 tests=FORGED_SPF_HELO, JMQ_SPF_NEUTRAL, KAM_DMARC_NONE, KAM_DMARC_STATUS, KHOP_HELO_FCRDNS, SPF_HELO_PASS, SPF_NEUTRAL, USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.2 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, 17 Mar 2020 03:13:22 -0000 On Mon, Mar 16, 2020 at 08:06:14PM -0700, Jim Wilson wrote: >I can't access sourceware git trees via ssh anymore, and I think it is >because of the hardware change. I see some other people have had >problems, but it isn't clear what the solution is. I have a 4K rsa2 >ssh key, and as far as I know that should still work. The key was >generated about 2.5 years ago. With "ssh -v -v -v -v gcc.gnu.org >alive" I see at the end > >debug1: Offering public key: RSA >SHA256:LysRamdWBr25XoOq/7loXtTDnNmEt5OgeTbms+uYY8M >/home/jimw/.ssh/id_gnu_rsa2 >debug3: send_pubkey_test >debug3: send packet: type 50 >debug2: we sent a publickey packet, wait for reply >debug3: receive packet: type 60 >debug1: Server accepts key: pkalg rsa-sha2-512 blen 535 >debug2: input_userauth_pk_ok: fp >SHA256:LysRamdWBr25XoOq/7loXtTDnNmEt5OgeTbms+uYY8M >debug3: sign_and_send_pubkey: RSA >SHA256:LysRamdWBr25XoOq/7loXtTDnNmEt5OgeTbms+uYY8M >debug3: send packet: type 50 >Connection closed by 2620:52:3:1:0:246e:9693:128c port 22 > >So it looks like the server will accept the key, and then it just >closes the connection with no explanation. Hi Jim, It looks like there was a configuration problem on our part. Does it work now? cgf