From: James Lewis Nance <jlnance@intrex.net>
To: linux-kernel@vger.kernel.org
Subject: Re: The NSA's Security-Enhanced Linux (fwd)
Date: Fri, 22 Dec 2000 20:13:06 -0500 [thread overview]
Message-ID: <20001222201306.A19951@bessie.dyndns.org> (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:
>
> 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)
I often wonder how many people know that a whole bunch of the Linux
networking code is Copyrighted by the NSA. I'm always waiting to
hear someone come up with a conspiracy theory about it on slashdot,
but I have never heard anyone mention it.
Jim
-
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-23 1:42 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
2000-12-23 1:13 ` James Lewis Nance [this message]
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=20001222201306.A19951@bessie.dyndns.org \
--to=jlnance@intrex.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®