From: Ian Lance Taylor <ian@airs.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Joe Buck <Joe.Buck@synopsys.COM>, overseers@sourceware.org
Subject: Re: ssh keys and the Debian breach
Date: Thu, 15 May 2008 05:01:00 -0000 [thread overview]
Message-ID: <m3skwk1aq4.fsf@gossamer.airs.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805142304250.28735@digraph.polyomino.org.uk>
"Joseph S. Myers" <joseph@codesourcery.com> writes:
> See ~gccadmin/weak-key-list for a list of some keys that need disabling.
> This is non-exhaustive because it only includes world-readable keys, and
> there were lots of warnings from the script about keys it couldn't parse
> or didn't have a blacklist for their key length; ssh-vulnkey might well
> produce a different list.
I have disabled those keys by adding a comment in the authorized_keys
file. I also ran the scanner as root and disabled a few other keys.
Ian
prev parent reply other threads:[~2008-05-15 3:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 23:06 Joe Buck
2008-05-14 23:56 ` Joseph S. Myers
2008-05-15 1:51 ` Joseph S. Myers
2008-05-15 5:01 ` Ian Lance Taylor [this message]
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=m3skwk1aq4.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=Joe.Buck@synopsys.COM \
--cc=joseph@codesourcery.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).