From: Chris Metcalf <cmetcalf@ezchip.com>
To: <overseers@sourceware.org>
Subject: Re: sourceware/gcc ssh public key analysis
Date: Thu, 21 Jan 2016 17:44:00 -0000 [thread overview]
Message-ID: <56A118D0.1060106@ezchip.com> (raw)
In-Reply-To: <20160112220927.53009.qmail@sourceware.org>
[-- 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
next parent reply other threads:[~2016-01-21 17:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160112220927.53009.qmail@sourceware.org>
2016-01-21 17:44 ` Chris Metcalf [this message]
[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
[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] <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
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=56A118D0.1060106@ezchip.com \
--to=cmetcalf@ezchip.com \
--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).