Re: sourceware/gcc ssh public key analysis

["Simon Martin" <simon@nasilyan.com>]

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

Hi,

After many years of inactivity, I’d like to get back to GCC 
development and therefore finally act on the email below.

Can you please replace the current (weak) key you have for me / 
simartin@gcc.gnu.org by the attached RSA one?

Thanks a lot!

Simon

On 12 Jan 2016, at 23:09, root@sourceware.org wrote:

> 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.
>
> FILENAME /home/simartin/.ssh/authorized_keys
> FILEDATE 2006-12-15
> RASH restricted shell, see 
> https://www.sourceware.org/sourceware/accountinfo.html
> DSA 1024: weak dsa 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>.

>
> Happy hacking!

[-- Attachment #2: id_rsa.pub --]
[-- Type: text/plain, Size: 744 bytes --]

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCuHQsePOghiV4DeqJ6Lg+Sl1M889qRGU+nw5yYsYqsKYko6gy2shxYeKJd8nR1wD2a/oZa8aohpW3OeJ0ajYJIk1iu7hCGjLM2dKCiUPrvHorDUkGRjpMxqpv2YNUVgyqkJ9hEnWg+ciDSMHP7hh2ORIV3ID4UyozGnnmAH6+QoBp6+8tQ7tAGRsSJJPOKhy/jY2WnSXP+MtZRSY7u7v93H+I4TEv5l68XunjDc5gOF8zxMpFVSDPMJDTLhi5hcmqM+YTUksbWiOHJB9gdSB+hPZp4CJVtFa3LEoWALpNZPhLSvM4G0GanDa5/q2QkLYQT96YRLz2oSkX9JyRrgXIWiTvXtnotYdeD6TPv8Ndy1onNHnsoSDEegF2Ma6tpcPuZA+s4yQ2l1XuoYbSIcku4J0JdhTN/PwA3p0ATAn/OydXKxBa8DlvsLKL8laMmCCJpvatZ7nBSh++7zFFOknFHmnkfBmPqWGgQ4W8yOo+wsTRXdllrlHF9bez0GeFBO/1bdmcq8FNAPue3XRWWf4oF1n/Uu2TSPF9XCUuScRgcXSsmttgifl5mWkBEYAwPkDA4JkRuqqZ15wB5xvZW8SnycgPUE1yElaPisE02hrk9sO/Bqs42/2ypp3qoGqaQ1d0DEC10qyc8QQ48JhBSuQLY9izzZPyH8qkySui28MAQLw== simon@lyton.local