[cfarm-users] [Fwd: Re: [Gcc-cfarm-users] gcc67 and gcc68: New AMD donated Ryzen processor machines]

[Robert Parlett]

Apologies, that last message was garbled.  What I meant to send -

My key too seems to be out of date.

As a stop-gap, rather than updating many users' keys, would it be
simpler to change /etc/ssh/sshd_config.

and add

PubkeyAcceptedKeyTypes=+ssh-dss

to the end.




On 21/05/17 12:49, Laurent GUERBY via cfarm-users wrote:
> -------- Forwarded Message --------
> From: Alexandre Oliva 
> Subject: Re: [Gcc-cfarm-users] gcc67 and gcc68: New AMD donated Ryzen
> processor machines
> Date: Sun, 21 May 2017 01:09:27 -0300
> Mailer: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
>
> On May 20, 2017, Ineiev <ineiev at gnu.org> wrote:
>
>> Unfortunately, neither works for me, as well as
>> "ssh ineiev at gcc10.fsffrance.org"; in all cases it suggests entering
>> my password.
> It could have to do with the kind of key.  I've personally had issues
> with certain key types: the old keys I registered many years ago still
> work on some machines, but some newer machines and/or my local hosts
> cannot use those key types any more, so I can't get into some of the
> newer machines, and I can't find out how to have my newer SSH keys
> propagated to the newer machines.
>
> A while ago, I sent an email following the procedure under "How to Get
> Involved?" in https://gcc.gnu.org/wiki/CompileFarm in an attempt to have
> the keys updated, to no avail: I never got a response.
>
> I didn't think a support request through the web site would have been
> workable: how would my account at the support site be tied to the
> existing login in the Compile Farm to tell whether the request was
> legitimate?  Anyway, I tried that too, but the password I had created at
> some point doesn't work any more, and the request to send it by email
> seems to go to a void, or to an address I can't get to any more.  And if
> I create a new account there, it would be even harder to connect it to
> my existing account in the farm, I suppose.
>
> Anyway, it would be nice to have a documented procedure in the wiki
> stating how to get SSH keys updated.  It might even be the case that the
> procedure to get an initial account needs updating, if the support site
> is the preferred way now.
>
> If someone (Laurent?) can tell me what the procedures to update SSH?
> keys is, and whether other procedures need updating in the wiki, I will
> update it there.
>
> Thanks,
>