From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jimw@sifive.com>
Received: from mail-vk1-xa2a.google.com (mail-vk1-xa2a.google.com
 [IPv6:2607:f8b0:4864:20::a2a])
 by sourceware.org (Postfix) with ESMTPS id B6B443942025
 for <overseers@sourceware.org>; Tue, 17 Mar 2020 03:06:26 +0000 (GMT)
Received: by mail-vk1-xa2a.google.com with SMTP id e20so5554699vke.9
 for <overseers@sourceware.org>; Mon, 16 Mar 2020 20:06:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=b7S8ZWbDBgjUoykxqWJLAMnXqCdFAUgWYKWGilUzmS0=;
 b=Ic0i4TKOddYQzz6fXiR3pTjeiiEA66qQy6YE/hLizM74aAR0TRPy9afLK/VWhoZvkx
 IsjhbsgGfG7ovmMB/KrM3N9oc4JVqyYOY2OwwSuC6BBz8k94eRhEeG8jIUjlRr5TrsJY
 sbGiPPY+PLUSjSmtJdqf27+tspV1oGM0kdXlxQkHzSRMZNJVZr1PRV4HpvxS4BUmS15p
 RjU2EC+WpGAuSeJORt3IZPFuxbRlHmrBSpAXAJBywk7atkRWFsj0qYwq6m9phPXq7mIv
 omRyhLKR5t2WnW1/rrcPSTF3HMu2RGz3I/JNIByXIS2vr4dBF9I5E3ge16zjF9BmO8vU
 y/CQ==
X-Gm-Message-State: ANhLgQ2e1wPQVEclcn4lIkLdTC5PIKjEIR0EMKD6Kau3h6Wx3z05au9z
 enObqj4GiXYKfI3tllKzD2cg1buyVo7knOTqZ7Sy+NGcAOc=
X-Google-Smtp-Source: ADFU+vvn7+qp066tfgnMSrzZFa5Xh1apCIa8DFWMkHXbhOl++UdwXAhDx0m0UoPxR+cUoDFDxx8ZhsdobJKRTHtCV48=
X-Received: by 2002:a1f:b401:: with SMTP id d1mr2185970vkf.26.1584414385777;
 Mon, 16 Mar 2020 20:06:25 -0700 (PDT)
MIME-Version: 1.0
From: Jim Wilson <jimw@sifive.com>
Date: Mon, 16 Mar 2020 20:06:14 -0700
Message-ID: <CAFyWVaYFh=J7qXCwKPaWEkE5EO0fUthjnD2CRK8=vpC_iXzuEQ@mail.gmail.com>
Subject: problems with ssh keys
To: overseers@sourceware.org
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED, DKIM_VALID,
 DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,
 SPF_PASS autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: overseers@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Overseers mailing list <overseers.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/overseers>,
 <mailto:overseers-request@sourceware.org?subject=unsubscribe>
List-Archive: <http://sourceware.org/pipermail/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/overseers>,
 <mailto:overseers-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2020 03:06:27 -0000

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.

Jim