Updating public key for sayle@gcc.gnu.org

Updating public key for sayle@gcc.gnu.org

[Roger Sayle]

[-- Attachment #1: Type: text/plain, Size: 4249 bytes --]


Dear Overseers,

Please can you update my public key on gcc.gnu.org?  It has been several
years since I last
tried using my sayle@gnu.org credentials, and although ssh
sayle@fencepost.gnu.org still
works, I've been having problems using ssh to check out the gcc tree with
the command:
git clone git+ssh://sayle@gcc.gnu.org/git/gcc.git

Many thanks to Joseph Myers (and Hans-Peter Nilsson) for diagnosing that the
problem
is with key pair I've been using 2002.  To quote Star Wars, "It's an older
code, but it checks
out".

I've now generated a new 4096-bit RSA key pair, and was wondering whether
you could
please update my access permissions/credentials on gcc.gnu.org with the
attached sayle.pub?
To help prove that this really is me, I've also uploaded the exact same file
as ~sayle/sayle.pub
on fencepost.gnu.org, which should at least prove that I have the old
private key.

Very many thanks in advance for your help.
Best regards (and stay safe),
Roger
--
Roger Sayle, PhD.
CEO and founder
NextMove Software Limited
Registered in England No. 07588305
Registered Office: Innovation Centre, 320 Cambridge Science Park, Cambridge,
CB4 0WG

-----Original Message-----
From: Joseph Myers <joseph@codesourcery.com> 
Sent: 22 June 2020 21:51
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Roger Sayle <roger@nextmovesoftware.com>; gcc-patches@gcc.gnu.org
Subject: RE: [PATCH] simplify-rtx: Two easy pieces.

On Sat, 20 Jun 2020, Hans-Peter Nilsson wrote:

> Hi!  Good to see you "back"!
> 
> On Sat, 20 Jun 2020, Roger Sayle wrote:
> > Thanks to you too.  Alas, my credentials from the CVS days of GCC 
> > almost certainly don't work any more (in git),
> 
> My guess is that your credentials are fine (possibly modulo FSF 
> assignment issues) if it wasn't for the ssh key for your account being 
> unacceptably short and/or DSA.  I'd suggest you generate a new 
> larger-than-X-bits RSA key (4096 should be good) and ask overseers@ to 
> install it for you.

In this particular case, the reason a new key is probably needed is that the
one currently installed for Roger's account is in SSH1 format (and SSH
protocol version 1 is long obsolete, and I don't think SSH servers accept
SSH1 format keys in authorized_keys for SSH protocol 2).

--
Joseph S. Myers
joseph@codesourcery.com

----
On Sat, 20 Jun 2020, Hans-Peter Nilsson wrote:
On Sat, 20 Jun 2020, Roger Sayle wrote:
>
> Hi Hans-Peter,
>
> I'm not sure how "back" I am, this might be just covid-related boredom.
>
> Is there any reason why "ssh sayle@fencepost.gnu.org" would work, but 
> "ssh sayle@gcc.gnu.org" doesn't?

Yes, there was a deliberate move disabling short and/or DSA keys a while ago
on sourceware.org / gcc.gnu.org.  Different machines and admins than for
fencepost.gnu.org.

...(searching)...

Looks like this happened in January 2016, and that people were sent email
with the subject "sourceware/gcc ssh public key analysis" that looked as
follows (quoting the one I was sent, excluding the part marked <deleted>):

--------------
Due to recent user reports of difficulty logging onto the server known as
sourceware.org / gcc.gnu.org / etc., we are scanning your installed ssh
public keys for continued compatibility.
Here is your analysis.

<deleted>

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>.

Happy hacking!
----------

> Specifically,
> % git clone git+ssh://sayle@gcc.gnu.org/git/gcc.git
>
> results in
> Cloning into 'gcc'...
> sayle@gcc.gnu.org: Permission denied (publickey).
> fatal: Could not read from remote repository.

To me it looks like a match.

> Forgive me, if I have my incantations wrong, but I've been assuming my 
> accounts had been disabled after all this time.  Discovering that I 
> can still check the copyright assignments on fencepost has been a 
> pleasant surprise.

I've never heard of those accounts being disabled for lack of activity,
unless perhaps if had shell access (as opposed to cvs, svn, git)?

> I'm happy to write to overseers@ once I've confirmed that I'm not 
> doing anything stupid.  Many thanks for your help.

Go for it!  HTH.  Keep healthy.
brgds, H-P


[-- Attachment #2: sayle.pub --]
[-- Type: application/octet-stream, Size: 762 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDKpAj98Vwx7xEtLufthyGTZzE6aKuIoVoUjlQ04df6CTU9daKrkMEKRZZwWbPrP1Zw+Kpdv7shcWRw9Gr34xUm97I8wJPqvsvWzK7rwEBNN6EjdrxfbAmQz9nH47+hcMAev2k4TmbIV1fr8xDSWYI9OReZdW8AsHJqVAC7n6ANgddu7xByvSoEKaLdXlGHcgKJlHqrv7l7jcgU+zsbJjgl6UMY/ZXpXVAfujTozj2bKb6zzHCQy8D5jbDY/Qv5X2VLIs6wR8pYPsyh4EZe2jOblS90Fp6z2CVd+gqjPn7rMxulhCmgzRBAGuerxpQ5RQtnwgoA7uk0fGDXMzroBaY9K2SkHu2sROV8Vj2UFyKOEW2yYSvuRA7D/Xl+Mm7Pmf8XhdJhXPox5jFK3CVnTTsHRFBaJd31mkJPvI/KTHSkkSHGAd1mnHUzbeUg8hpqwB0m+5Rl3m0VToS4Hd90EycKoyad6MsaRyVldnmVfnUupAcXu0PkRgU/qtzTu41K8RwCxzCNs76n7hh5lYLCeg3rIgTdc0CaynXdH/+uCOWgolfkUmd2QulFVpovJNnF5/lQY3BP4hm/5AfT8wZpUtuGVZzRGwaeb1eLxkejJOPdkxomDBXeS4G9oOnLX0GdoyUZccYJfLc0c35/PRKycqWj4elH2WeYzzWBuVwQRURWiw== roger@nextmove.nextmovesoftware.com

Re: Updating public key for sayle@gcc.gnu.org

[Mark Wielaard]

Hi Rogers,

On Sat, Jun 27, 2020 at 09:00:00PM +0100, Roger Sayle via Overseers wrote:
> I've now generated a new 4096-bit RSA key pair, and was wondering
> whether you could please update my access permissions/credentials on
> gcc.gnu.org with the attached sayle.pub?  To help prove that this
> really is me, I've also uploaded the exact same file as
> ~sayle/sayle.pub on fencepost.gnu.org, which should at least prove
> that I have the old private key.

Welcome back Jedi. New code accepted and installed.

Cheers,

Mark