From: Ed Smith-Rowland <3dw4rd@verizon.net>
To: overseers@sourceware.org, root@sourceware.org
Subject: Re: sourceware/gcc ssh public key analysis
Date: Sat, 7 Mar 2020 13:47:55 -0500 [thread overview]
Message-ID: <e4912ba9-31f4-58ff-854a-783af7d5eaa3@verizon.net> (raw)
In-Reply-To: <20160112220930.55610.qmail@sourceware.org>
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
next parent reply other threads:[~2020-03-07 20:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160112220930.55610.qmail@sourceware.org>
2020-03-07 18:47 ` Ed Smith-Rowland [this message]
[not found] <20160112220951.69787.qmail@sourceware.org>
[not found] ` <2F12E318-AF48-47F5-98D0-03421055FE59@nasilyan.com>
2024-03-23 15:32 ` Simon Martin
2024-03-23 21:56 ` Mark Wielaard
[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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4912ba9-31f4-58ff-854a-783af7d5eaa3@verizon.net \
--to=3dw4rd@verizon.net \
--cc=overseers@sourceware.org \
--cc=root@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).