problems with ssh keys

problems with ssh keys

[Jim Wilson]

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

Re: problems with ssh keys

[Christopher Faylor]

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

Re: problems with ssh keys

[Jim Wilson]

On Mon, Mar 16, 2020 at 8:06 PM Jim Wilson <jimw@sifive.com> wrote:
> I can't access sourceware git trees via ssh anymore, ...

Actually, it is working now.  So maybe it was a temporary hiccup on
the server side.

Jim

Re: problems with ssh keys

[Christopher Faylor]

On Mon, Mar 16, 2020 at 08:22:55PM -0700, Jim Wilson wrote:
>On Mon, Mar 16, 2020 at 8:06 PM Jim Wilson <jimw@sifive.com> wrote:
>> I can't access sourceware git trees via ssh anymore, ...
>
>Actually, it is working now.  So maybe it was a temporary hiccup on
>the server side.

Hi Jim,
I tried to send you a message indicating that I probably fixed the
problem but mailman apparently insisted that I needed to reply only to
overseers.  Looks like I need to tweak my email configuration a bit.

For the record, it was a password file configuraiton error on our
part.

Glad to hear that what I did solved your problem.

cgf