From: "Michael H. Warfield" <mhw@wittsend.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Sandy Harris <sandy@storm.ca>, linux-kernel@vger.kernel.org
Subject: Re: The NSA's Security-Enhanced Linux (fwd)
Date: Fri, 22 Dec 2000 14:38:13 -0500 [thread overview]
Message-ID: <20001222143813.C30319@alcove.wittsend.com> (raw)
In-Reply-To: <3A439833.C64D493A@storm.ca> <E149X6e-000525-00@the-village.bc.nu>
In-Reply-To: <E149X6e-000525-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, Dec 22, 2000 at 06:39:49PM +0000
On Fri, Dec 22, 2000 at 06:39:49PM +0000, Alan Cox wrote:
> > These folks are good at what they do and the code is GPL.
> > It is worth starting to consider whether this code, or code
> > from one of the other security-enhancement projects, should
> > be included in the standard kernel for 2.6 or 3.0.
> I think this is a good point. Its actually a nice testimonial for free
> software that its finally got the NSA contributing code in a way that everyone
> benefits from and which may help cut down computer crime beyond government.
> (and which of course actually is part of the NSA's real job)
> > > It's just code like everone else produces.
> > So people looking at it may find bugs and vulnerabilities the
> > implementers hadn't considered. Great.
> Yep. Im sure all sorts of people will be finding bugs in it because they are
> looking for secret NSA backdoors so why discourage them 8)
Now that's a real damn good point that I hadn't thought of.
With everyone so paranoid about what backdoors they may have left (like
they would be that crazy to put them in and put it out in plain view
for everyone) that the code should end up getting a real good review
for bugs as well. :-) Such a deal. :-)
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
(The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-22 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91uu8i$f1nrj$1@fido.engr.sgi.com>
2000-12-22 17:52 ` Casey Schaufler
2000-12-22 18:06 ` Sandy Harris
2000-12-22 18:39 ` Alan Cox
2000-12-22 19:38 ` Michael H. Warfield [this message]
2000-12-23 1:13 ` James Lewis Nance
2000-12-23 1:36 ` Alex Belits
2000-12-23 6:24 ` Andre Hedrick
2000-12-23 4:22 ` Kurt Garloff
2000-12-27 12:48 ` Stephen Smalley
2000-12-22 7:00 Mike A. Harris
2000-12-22 10:39 ` Alex Buell
2000-12-22 15:06 ` Michael H. Warfield
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=20001222143813.C30319@alcove.wittsend.com \
--to=mhw@wittsend.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sandy@storm.ca \
/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
all inboxes | Powered by JetHome®