Git over SSH access problem

Git over SSH access problem

[Eli Zaretskii]

Today I cannot access the sourceware Git repository for Binutils and
GDB: Git says it cannot use my private SSH key.  I have been using
this key to access sourceware.org repositories for ages, last time
this May.

Could someone please help me understand what's wrong with my access
method and how to fix it, so I will be once again able to access the
Git repositories?

TIA

Re: Git over SSH access problem

[Frank Ch. Eigler]

Hi -

> Today I cannot access the sourceware Git repository for Binutils and
> GDB: Git says it cannot use my private SSH key.  I have been using
> this key to access sourceware.org repositories for ages, last time
> this May.

# ssh-key-doctor eliz

[...]

FILENAME /home/eliz/.ssh/authorized_keys
FILEDATE 2005-12-08
RASH restricted shell, see https://www.sourceware.org/sourceware/accountinfo.html
RSA1 1024: already unsupported ssh1 key

You have no strong keys.  If you still need access to sourceware/gcc,
consider generating new key-pair with   % ssh-keygen -t rsa -b 4096
and if necessary, sending the .pub part to <overseers@sourceware.org>.



I'm surprised if it has worked for you so recently.  Please generate
a new keypair as per the above instructions.


- FChE

Re: Git over SSH access problem

[Eli Zaretskii]

> Date: Thu, 18 Jul 2019 09:05:31 -0400
> From: "Frank Ch. Eigler" <fche@elastic.org>
> Cc: overseers@sourceware.org
> 
> FILENAME /home/eliz/.ssh/authorized_keys
> FILEDATE 2005-12-08
> RASH restricted shell, see https://www.sourceware.org/sourceware/accountinfo.html
> RSA1 1024: already unsupported ssh1 key
> 
> You have no strong keys.  If you still need access to sourceware/gcc,
> consider generating new key-pair with   % ssh-keygen -t rsa -b 4096
> and if necessary, sending the .pub part to <overseers@sourceware.org>.

Yes, I need to access sourceware, as I'm one of the GDB developers.

I have a v2 key pair already.  I attach its .pub part below.  Is this
key okay?  If yes, do I need to do anything else, besides configuring
on my side to use this key for sourceware?

Thanks.

======================================================================
---- BEGIN SSH2 PUBLIC KEY ----
Comment: "eliz@elta"
AAAAB3NzaC1yc2EAAAABJQAAAIEAhkN/tABTeQ4+O6Qtt50+E7feYrvBfE7g7FSx
oysIUC1WThAXCLIaebxMeXk0xECg5NJ1qw4+C69HqpT0vOmQHCtoZTsG+V+4tr4z
hgHWljOZdeuAy8Qj3g+wt/EM/E650kwqbbvvRUzKvKjPV2oDU5t10zDTbrOAo4nH
4bL71Hs=
---- END SSH2 PUBLIC KEY ----

Re: Git over SSH access problem

[Frank Ch. Eigler]

Hi -

> I have a v2 key pair already.  I attach its .pub part below.  Is this
> key okay?

No, it looks like an EC type key, which is not supported by rhel6 ssh
on sourceware, not an RSA one.

> If yes, do I need to do anything else, besides configuring on my
> side to use this key for sourceware?

That part is automatic.  Your ssh client will try all the keys it
knows about.

- FChE

Re: Git over SSH access problem

[Eli Zaretskii]

> Date: Thu, 18 Jul 2019 10:26:33 -0400
> From: "Frank Ch. Eigler" <fche@elastic.org>
> Cc: overseers@sourceware.org
> 
> > I have a v2 key pair already.  I attach its .pub part below.  Is this
> > key okay?
> 
> No, it looks like an EC type key, which is not supported by rhel6 ssh
> on sourceware, not an RSA one.

What about the one below?

> > If yes, do I need to do anything else, besides configuring on my
> > side to use this key for sourceware?
> 
> That part is automatic.  Your ssh client will try all the keys it
> knows about.

Thanks.


---- BEGIN SSH2 PUBLIC KEY ----
Comment: "rsa-key-20190718"
AAAAB3NzaC1yc2EAAAABJQAAAgBqqWa7E3D4DpCewcoYm659RG95GEEhwkVRNRps
jVXXtG3xKkcp0fl2IZngf4q01skSkVVYdexgxyENwaEitcQUH/A/6p7MLFDt7sQi
UATabMB5J3VhLuNDLqL6SScRBXV0cx0uORw42bo1U5V/4nYTrFHZ984MBahbL3+g
3lIUfVVN4iaaYaDOmB5zKfLiuvZngHhXZ0tVR5h0djtbkTfvd6la3LdkEC0qfJnv
LXq9hw22rM24Hzes++HuV63mJV/ecpUfKuAw3xHr+/CuINCPWnpJ/+XVt0mWwOGL
wRtWAvmy4cMSU9vuapfXYGfQqE2Ca114R2qac8QkY+D4CXDbXV9HR+QekJPBulBK
XMW6hYossuMZTRja7T6D65Xi65xcK52Vap9sUcANosCZRVM0YqhGFVhVIW4/PUh1
GEdRI0EuFFuHSuoT/J16bBSKdSeQaVFSWIoojqGBmR5XjDdfb+uK4WIqUanukFM2
MMPPwP7csgHGpiezcBOb0oJ8YdxiaYt6MhuWEI8Poq1ujy36SS5IAQvGXt/AloJE
4ZIdktFaJ3Cu0I4UuIJETDHUZJK4de7Imhif2jT7Ya5f025Vsro4ehmEdb3g/q0N
ryCaB0cnSH/IF3hDSsMlJxPsXYP4ZLHPwg/rFcgi2S9asBvAt2NI2HqpoSm2FxK0
3hXykQ==
---- END SSH2 PUBLIC KEY ----

Re: Git over SSH access problem

[Frank Ch. Eigler]

Hi -

> What about the one below?

That one looks good.

- FChE

Re: Git over SSH access problem

[Eli Zaretskii]

> Date: Thu, 18 Jul 2019 10:43:01 -0400
> From: "Frank Ch. Eigler" <fche@elastic.org>
> Cc: overseers@sourceware.org
> 
> > What about the one below?
> 
> That one looks good.

Thanks, so now I should wait for overseers to install it and ack?

Re: Git over SSH access problem

[Frank Ch. Eigler]

Hi -

> > > What about the one below?
> > That one looks good.
> 
> Thanks, so now I should wait for overseers to install it and ack?

It has been installed.

- FChE

Re: Git over SSH access problem

[Eli Zaretskii]

> Date: Thu, 18 Jul 2019 10:53:06 -0400
> From: "Frank Ch. Eigler" <fche@elastic.org>
> Cc: overseers@sourceware.org
> 
> It has been installed.

Great, it works again.  Thank you very much for all your help.

Re: Git over SSH access problem

[Martin Sebor]

On 7/18/19 8:26 AM, Frank Ch. Eigler wrote:
> Hi -
> 
>> I have a v2 key pair already.  I attach its .pub part below.  Is this
>> key okay?
> 
> No, it looks like an EC type key, which is not supported by rhel6 ssh
> on sourceware, not an RSA one.

I asked this once before but I don't think I heard back: could
the sourceware account information page be updated with the details
of what kinds of SSH keys are supported?  I also had trouble with
my account sometime ago and it was only by trial and error that
I was able to figure out I was using the wrong kind of key.

Thanks
Martin

> 
>> If yes, do I need to do anything else, besides configuring on my
>> side to use this key for sourceware?
> 
> That part is automatic.  Your ssh client will try all the keys it
> knows about.
> 
> - FChE
>