From: Ken Brown <kbrown@cornell.edu>
To: overseers@sourceware.org
Subject: Fwd: sourceware/gcc ssh public key analysis
Date: Wed, 13 Jan 2016 13:32:00 -0000 [thread overview]
Message-ID: <569651DA.9000307@cornell.edu> (raw)
In-Reply-To: <20160112220935.60829.qmail@sourceware.org>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
New key is attached.
-------- Forwarded Message --------
Subject: sourceware/gcc ssh public key analysis
Date: Tue, 12 Jan 2016 22:09:35 +0000
From: root@sourceware.org
To: kbrown@sourceware.org
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/kbrown/.ssh/authorized_keys
FILEDATE 2013-06-20
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!
[-- Attachment #2: id_rsa.pub --]
[-- Type: application/vnd.ms-publisher, Size: 740 bytes --]
next parent reply other threads:[~2016-01-13 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160112220935.60829.qmail@sourceware.org>
2016-01-13 13:32 ` Ken Brown [this message]
2016-01-14 4:12 ` Ian Lance Taylor
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=569651DA.9000307@cornell.edu \
--to=kbrown@cornell.edu \
--cc=overseers@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).