From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Overseers mailing list <overseers@sourceware.org>
Subject: Re: problems with ssh keys
Date: Mon, 16 Mar 2020 23:13:19 -0400 [thread overview]
Message-ID: <20200317031318.GA977@cgf.cx> (raw)
In-Reply-To: <CAFyWVaYFh=J7qXCwKPaWEkE5EO0fUthjnD2CRK8=vpC_iXzuEQ@mail.gmail.com>
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
next prev parent reply other threads:[~2020-03-17 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 3:06 Jim Wilson
2020-03-17 3:13 ` Christopher Faylor [this message]
2020-03-17 3:22 ` Jim Wilson
2020-03-17 3:34 ` 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=20200317031318.GA977@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=overseers@sourceware.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).