* Re: sourceware/gcc ssh public key analysis
[not found] ` <2F12E318-AF48-47F5-98D0-03421055FE59@nasilyan.com>
@ 2024-03-23 15:32 ` Simon Martin
2024-03-23 21:56 ` Mark Wielaard
0 siblings, 1 reply; 28+ messages in thread
From: Simon Martin @ 2024-03-23 15:32 UTC (permalink / raw)
To: overseers; +Cc: simartin
[-- 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
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: sourceware/gcc ssh public key analysis
2024-03-23 15:32 ` sourceware/gcc ssh public key analysis Simon Martin
@ 2024-03-23 21:56 ` Mark Wielaard
0 siblings, 0 replies; 28+ messages in thread
From: Mark Wielaard @ 2024-03-23 21:56 UTC (permalink / raw)
To: Simon Martin via Overseers; +Cc: Simon Martin, simartin
Hi Simon,
On Sat, Mar 23, 2024 at 03:32:37PM +0000, Simon Martin via Overseers wrote:
> After many years of inactivity, I’d like to get back to GCC
> development and therefore finally act on the email below.
Wow, nice archive. And welcome back! That email was certainly a long
time ago. I see your commit access was originally acked by Mark
Mitchell. And you were using a users.sourceforge.net account back
then. Does that still work?
> Can you please replace the current (weak) key you have for me /
> simartin@gcc.gnu.org by the attached RSA one?
Note that we use a private list admin-requests@sourceware.org instead
of this public mailinglist for account issues these days.
And since Mark Mitchell isn't around anymore, could you get one of the
gcc maintainers to ack your return?
See https://gcc.gnu.org/gitwrite.html#authenticated
Thanks,
Mark
^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <20160112220930.55610.qmail@sourceware.org>]
* Re: sourceware/gcc ssh public key analysis
[not found] <20160112220930.55610.qmail@sourceware.org>
@ 2020-03-07 18:47 ` Ed Smith-Rowland
0 siblings, 0 replies; 28+ messages in thread
From: Ed Smith-Rowland @ 2020-03-07 18:47 UTC (permalink / raw)
To: overseers, root
On 1/12/16 5:09 PM, 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/emsr/.ssh/authorized_keys
> FILEDATE 2012-02-22
> 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!
Here is a new RSA password file generated as recommended.
Ed Smith-Rowland
ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAACAQCotudyVyDRHSQayaPQQUgWPPbPHCZf1+nu6Dt5gwa4L2lzkut14cG2+f4iBKBg68JA3GCIo5+ckMo6hivYAVQ6oouJSrqCJbWEfteryDU/X35PYxe6rZzIOmrSkYI8YtqATxGRDc8dbEUuCgkz3rrd73d27vi0VGUgeHKQBAjP/weDLzLf0kyGnmNRR6+HKu5Gj28ndjioVEsv283dhiJhkRC8WOTQC+URTTHVJFBQEh+qfk054Q/ro1Ts1QDzBlO7E2zBJJvr0NIXmEWVa0bCaoMxBtkgELXjM8+Kec3Zdm9vkopxybUwhiabW1X8A95FXkUu4/Xtr9CPlSOTV8/JFjIPacHZJdN42A4q5dqcrTybz6TIr2ORxo3YJs4AtNahNlY6EsKjqNM54a0365dEywZWycN8dk/FsZSf1TJVxHZaOLt1tZnN+OBTmUGh6QeTRrHXoLjm+xDSwbQZ3+obo7PqQxBSzxdplqs7VIUmuVrLPsWmF1GHuQrn9iJdOi9Y3SY/Vg2kQJbfoI3HN7Xis3g7x+uIeLFi1HSMfUGpiwwEF2U63RWMf8NO0HpAjETJjS7+EdWWEBQLfW/nUomH2Ooucy33xvKkgx1z5peTzWIg0MZBJdAFwznkUm/vWJtcLrtec/myDuVRM5U9DlKIal/1bWx4k5CSoYXsGgI8yQ==
ed@bad-horse
^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <20160112220955.73318.qmail@sourceware.org>]
* Re: sourceware/gcc ssh public key analysis
[not found] <20160112220955.73318.qmail@sourceware.org>
@ 2016-03-08 16:00 ` Zack Weinberg
0 siblings, 0 replies; 28+ messages in thread
From: Zack Weinberg @ 2016-03-08 16:00 UTC (permalink / raw)
To: overseers
On Tue, Jan 12, 2016 at 5:09 PM, <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.
> : unknown type 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 do not need ssh access to sourceware/gcc at this time, and any ssh
keys you have for me are at least ten years old and should be deleted.
zw
^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <20160112220953.71700.qmail@sourceware.org>]
[parent not found: <20160112220927.53009.qmail@sourceware.org>]
* Re: sourceware/gcc ssh public key analysis
[not found] <20160112220927.53009.qmail@sourceware.org>
@ 2016-01-21 17:44 ` Chris Metcalf
[not found] ` <20160126162348.GA14318@elastic.org>
0 siblings, 1 reply; 28+ messages in thread
From: Chris Metcalf @ 2016-01-21 17:44 UTC (permalink / raw)
To: overseers
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Here is a new key following your directions (attached). Thanks!
On 01/12/2016 05:09 PM, 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/cmetcalf/.ssh/authorized_keys
> FILEDATE 2011-11-20
> RASH restricted shell, see https://www.sourceware.org/sourceware/accountinfo.html
> RSA 1024: weak rsa 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!
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
[-- Attachment #2: id_rsa_ezchip.pub --]
[-- Type: text/plain, Size: 741 bytes --]
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAgEA7raywstbrqtFK/sVGd8Y/1h7mY0uqvbvjgjMod1eEUxxXAE02xLGyd4rP1NN2jwnituDfNn+uprOMwc5ap7s8aL8wvo1ZMkbDnHZcuz3Usvd5HKbZMOKqumeKdgMKw5tg+JnwTBmcRTbxMmaX+q334+3UuscxMZfp2A7JVR09dT4e5gfKmv7hdPTytc6UMQWdqhpiZhUT4aPRy8H9BFbRPuAwc7zT4wAh8or8Za3e2zEofcrN/9bo31G/15m2L78yjTijwWGtlo/BfnBgMVoN6Au3G7nxszEbWdajjcJimHKJ3x/WfXXKEI91C7kGGWFUoPkEZg5dNFn88mrVV35PBjyABLyHXNIVehq2GJ0OUtdpYt81JsT5IGx5JKUzddRhRDAm9qxxVj3i5PgMHxraA8kl4if59rD/s0VsjYsm7emQ7cmxc9ZK46CJxyD0pp8hzPHE/IfICmgqnDOCwG2asOPiW/LYBYc+/i6+xSRF/G28RJjK67oCg+qKb8UeZvMOhTJde7D2diyx1zD1S6t0HzIkm2qaLCPMhheha3X9kGuJSyo2hNa0L912mYfYFyS9nbcA1qcPqVlbHf3mQ9vFYHu6NriN8kU6i0vBia02VZ6w8im3SUC9eMQ654wII3+rHXmD5Gw/DUVefjMr68pLO7+oq5mEQKduYtawWEdbW0= cmetcalf@ezchip.com
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: sourceware/gcc ssh public key analysis
@ 2016-01-21 12:54 Alfred M. Szmidt
2016-01-21 15:06 ` Ian Lance Taylor
0 siblings, 1 reply; 28+ messages in thread
From: Alfred M. Szmidt @ 2016-01-21 12:54 UTC (permalink / raw)
To: overseers
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.
Here is a new key, could someone update /home/amszmidt/.ssh/authorized_keys ?
ssh-rsa AAAAB3NzaC1yc2EAAAAEOyN9vwAAAQEAoM8eyzmC7nS4msuEcxwwwZ9HdJGMEiPOCkdqUlIsad8PN2UyB0JJojR3XQsB1QpL3C9boCiiCHQbTExw+aHsi8UpVcY+yi9wDQhNWDJAWDgBPKA4ii5OjTXcoZrDjLtBU+07h8ZY1E10S6T4ZEfxhmUL+PXngR7kHIH6RqTgkbvUtMNl0tXDLSm1CkmV/6xEWspT/lRiI0T1OqEfnIATfP7b708NC2mCLFmp39lrqintNa4ch9ej1OgHUTBNIzxd8XOb5LbkeLjl6H+7PBGbQrsecho4HqgJAqjdSb0yo7NJjclUvsCJ6INVe2CEMVy/Itsd8i6a325dI3VEKzG26Q==
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: sourceware/gcc ssh public key analysis
2016-01-21 12:54 Alfred M. Szmidt
@ 2016-01-21 15:06 ` Ian Lance Taylor
2016-01-21 15:45 ` Alfred M. Szmidt
0 siblings, 1 reply; 28+ messages in thread
From: Ian Lance Taylor @ 2016-01-21 15:06 UTC (permalink / raw)
To: Alfred M. Szmidt; +Cc: overseers
ams@gnu.org (Alfred M. Szmidt) writes:
> 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.
>
> Here is a new key, could someone update /home/amszmidt/.ssh/authorized_keys ?
Done.
Ian
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: sourceware/gcc ssh public key analysis
2016-01-21 15:06 ` Ian Lance Taylor
@ 2016-01-21 15:45 ` Alfred M. Szmidt
0 siblings, 0 replies; 28+ messages in thread
From: Alfred M. Szmidt @ 2016-01-21 15:45 UTC (permalink / raw)
To: Ian Lance Taylor; +Cc: overseers
> 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.
>
> Here is a new key, could someone update
> /home/amszmidt/.ssh/authorized_keys ?
Done.
Thanks!
^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <20160112220924.50203.qmail@sourceware.org>]
[parent not found: <20160112220949.67993.qmail@sourceware.org>]
* Re: sourceware/gcc ssh public key analysis
[not found] <20160112220949.67993.qmail@sourceware.org>
@ 2016-01-14 12:30 ` Ricard Wanderlof
2016-01-14 18:14 ` Frank Ch. Eigler
0 siblings, 1 reply; 28+ messages in thread
From: Ricard Wanderlof @ 2016-01-14 12:30 UTC (permalink / raw)
To: overseers
Hi,
A while ago I updated my public key, so I'd like to get it updated at
sourceware.org also:
ssh-rsa
AAAAB3NzaC1yc2EAAAADAQABAAABAQCp+vswJSnLHcx1bzam9HR6RFokkckMvAcByE4upGQkt6C+QnI9a2YW6/KaA/T3ScXq6fdmFMvDobWYwaCkIJ8XK11twYhu1Rtx8HSxAMyHL+amf9b+D1zHNY/d86+bmoo8rmle05JpdSFRxoK/BOv5/E2BjP0PCe06kQ4CPfGfIR8MLr/XTgZZEGwZg3jgFE2Koaeso52AAPLPlGdRisD02yvG1GMsqkJZTHWwQnYps8insk1ltmyFpw70PCio53R43vFA5WFVAJYBFFRw7VEQj4BTL1Bmco+JOQSK5sBd5f3a+nb2wjX/vbH233r7rVJdhF6bo610kJg9SDRGfUT/
ricardw@lnxricardw1
/Ricard
--
Ricard Wolf Wanderlöf ricardw(at)axis.com
Axis Communications AB, Lund, Sweden www.axis.com
Phone +46 46 272 2016 Fax +46 46 13 61 30
^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <20160112220949.67889.qmail@sourceware.org>]
[parent not found: <20160112220925.51505.qmail@sourceware.org>]
* Re: sourceware/gcc ssh public key analysis
[not found] <20160112220925.51505.qmail@sourceware.org>
@ 2016-01-13 10:31 ` Brian Gough
2016-01-13 15:00 ` Christopher Faylor
0 siblings, 1 reply; 28+ messages in thread
From: Brian Gough @ 2016-01-13 10:31 UTC (permalink / raw)
To: overseers
You can remove the account below, it is no longer in use. Thank you.
On 12/01/16 22: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/bjg/.ssh/authorized_keys
> FILEDATE 2008-05-21
> SHELL you have shell access
> RSA 1024: weak rsa 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!
^ permalink raw reply [flat|nested] 28+ messages in thread
* Re: sourceware/gcc ssh public key analysis
2016-01-13 10:31 ` Brian Gough
@ 2016-01-13 15:00 ` Christopher Faylor
0 siblings, 0 replies; 28+ messages in thread
From: Christopher Faylor @ 2016-01-13 15:00 UTC (permalink / raw)
To: overseers, Brian Gough
On Wed, Jan 13, 2016 at 10:31:37AM +0000, Brian Gough wrote:
>On 12/01/16 22: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/bjg/.ssh/authorized_keys
>> FILEDATE 2008-05-21
>> SHELL you have shell access
>> RSA 1024: weak rsa 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!
>
>You can remove the account below, it is no longer in use. Thank you.
Thanks for letting us know.
Account removed.
^ permalink raw reply [flat|nested] 28+ messages in thread
[parent not found: <20160112220924.50132.qmail@sourceware.org>]
[parent not found: <20160112220926.52144.qmail@sourceware.org>]
[parent not found: <20160112220954.72461.qmail@sourceware.org>]
end of thread, other threads:[~2024-03-23 21:56 UTC | newest]
Thread overview: 28+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20160112220951.69787.qmail@sourceware.org>
[not found] ` <2F12E318-AF48-47F5-98D0-03421055FE59@nasilyan.com>
2024-03-23 15:32 ` sourceware/gcc ssh public key analysis Simon Martin
2024-03-23 21:56 ` Mark Wielaard
[not found] <20160112220930.55610.qmail@sourceware.org>
2020-03-07 18:47 ` Ed Smith-Rowland
[not found] <20160112220955.73318.qmail@sourceware.org>
2016-03-08 16:00 ` Zack Weinberg
[not found] <20160112220953.71700.qmail@sourceware.org>
2016-02-18 13:35 ` Tom Tromey
2016-02-18 15:30 ` Frank Ch. Eigler
[not found] <20160112220927.53009.qmail@sourceware.org>
2016-01-21 17:44 ` Chris Metcalf
[not found] ` <20160126162348.GA14318@elastic.org>
2016-07-05 21:20 ` Chris Metcalf
2016-07-05 21:40 ` Christopher Faylor
2016-07-05 21:49 ` Christopher Faylor
2016-07-06 0:43 ` Chris Metcalf
2016-01-21 12:54 Alfred M. Szmidt
2016-01-21 15:06 ` Ian Lance Taylor
2016-01-21 15:45 ` Alfred M. Szmidt
[not found] <20160112220924.50203.qmail@sourceware.org>
2016-01-17 2:29 ` Joern Wolfgang Rennecke
[not found] <20160112220949.67993.qmail@sourceware.org>
2016-01-14 12:30 ` Ricard Wanderlof
2016-01-14 18:14 ` Frank Ch. Eigler
[not found] <20160112220949.67889.qmail@sourceware.org>
2016-01-13 20:55 ` Volker Reichelt
[not found] <20160112220925.51505.qmail@sourceware.org>
2016-01-13 10:31 ` Brian Gough
2016-01-13 15:00 ` Christopher Faylor
[not found] <20160112220924.50132.qmail@sourceware.org>
2016-01-13 9:39 ` Andrew Stubbs
2016-01-13 13:21 ` Ian Lance Taylor
[not found] <20160112220926.52144.qmail@sourceware.org>
2016-01-13 7:07 ` Tobias Burnus
2016-01-13 13:20 ` Ian Lance Taylor
[not found] <20160112220954.72461.qmail@sourceware.org>
[not found] ` <569598D0.9010304@redhat.com>
2016-01-13 0:27 ` Vladimir Makarov
2016-01-13 1:34 ` Ian Lance Taylor
2016-01-13 3:42 ` Vladimir Makarov
2016-01-13 10:48 ` Gerald Pfeifer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).