public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: grossman@gcc.gnu.org, korbb@gcc.gnu.org, mbroz@gcc.gnu.org,
	ostrichfly@gcc.gnu.org, schauer@gcc.gnu.org, zhaolei@gcc.gnu.org
Cc: overseers@gcc.gnu.org
Subject: Possible weak SSH keys
Date: Thu, 15 May 2008 03:57:00 -0000	[thread overview]
Message-ID: <m3tzh0tp89.fsf@google.com> (raw)

Recent reports of problems with SSH keys generated on Debian systems
led us to scan the SSH keys on gcc.gnu.org aka sourceware.org.  If you
are in the To: of this message, at least one of your SSH keys was
listed as "no suitable blacklist" by the SSH key check script that we
ran.  This does not necessarily indicate a problem.  But we would like
each of you to check your SSH keys.  If you generated it on a Debian
system since 2006-09-17, please generate a new key and send it to us.
Otherwise, please confirm that your SSH keys are OK.

For background, see:

http://blog.drinsama.de/erich/en/linux/2008051401-consequences-of-sslssh-weakness.html

Thanks.

Ian

                 reply	other threads:[~2008-05-14 23:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m3tzh0tp89.fsf@google.com \
    --to=iant@google.com \
    --cc=grossman@gcc.gnu.org \
    --cc=korbb@gcc.gnu.org \
    --cc=mbroz@gcc.gnu.org \
    --cc=ostrichfly@gcc.gnu.org \
    --cc=overseers@gcc.gnu.org \
    --cc=schauer@gcc.gnu.org \
    --cc=zhaolei@gcc.gnu.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).