From: "Admissions Office" <admissions@internet.edu.nf>
To: "McFadden, Ken" <ken.mcfadden@lmco.com>,
"'Russell Coker'" <russell@coker.com.au>,
"JW" <jw@centraltexasit.com>, "SE Linux" <selinux@tycho.nsa.gov>
Cc: "Haigh, Tom" <tom_haigh@securecomputing.com>,
"Carsten Grohmann" <carsten.grohmann@dr-baldeweg.de>
Subject: Re: Sorry, read this one: Re: SELinux Dumb Questions
Date: Tue, 4 Jun 2002 19:34:16 -0600 [thread overview]
Message-ID: <010001c20c31$1b799980$91c03b8e@OK> (raw)
In-Reply-To: 31A81CDD9175D411815100508BE32AA60142F388@emss02m13.ems.lmco.com
Ok but, lets not let emotions rule the day. The NSA has done us all a
service and we them. So in the true spirit of the internet lets work this
out. Tom & I are playing phone tag but, we will speak.... And I bet we will
have something to report back. No big deal !
Really.
----- Original Message -----
From: "McFadden, Ken" <ken.mcfadden@lmco.com>
To: "'Russell Coker'" <russell@coker.com.au>; "JW" <jw@centraltexasit.com>;
"SE Linux" <selinux@tycho.nsa.gov>
Cc: "Haigh, Tom" <tom_haigh@securecomputing.com>; "'Admissions Office'"
<admissions@internet.edu.nf>; "Carsten Grohmann"
<carsten.grohmann@dr-baldeweg.de>
Sent: Tuesday, June 04, 2002 16:28
Subject: RE: Sorry, read this one: Re: SELinux Dumb Questions
> Once again, We are doing this for NSA and GNU NOT SECURE COMPUTING!!!!!!!
> If Tom has a problem then they need to address it with the NSA and the
> NSA can go forth and remove their crap or deem it as being GNU.....As I
> see it SELinux will go on and if someone would like to use it then all
> they would need to do is keep the original GNU licensing with it.....
> Other words this is not our problem to work out but Tom's and
NSA's........
> Until then I would treat it as GNU per NSA's web page!!!!!!!
>
>
>
>
> -----Original Message-----
> From: Russell Coker [mailto:russell@coker.com.au]
> Sent: Tuesday, June 04, 2002 4:12 PM
> To: JW; SE Linux
> Cc: Haigh, Tom; 'Admissions Office'; Carsten Grohmann
> Subject: Re: Sorry, read this one: Re: SELinux Dumb Questions
>
>
> On Tue, 4 Jun 2002 23:49, JW wrote:
> > Sorry about that last empty message, I accidently hit ^[ENTER] when I
> meant
> > hit shift...
>
> You had written enough to clarify the issue (I don't know how I missed
Tom's
>
> message the first time).
>
> > IANAL, but it is my understanding that you cannot restrict the use or
> > distribution of GPLd Free Software. It simply does not work that way, no
> > exceptions, no excuses. Once code is GPLd it is free for all to use. You
> > can change the license on future versions of the code, but you cannot go
> > back and restrict GPL's code "after the fact"
>
> Yes. Unless of course they claim that they didn't GPL it, or that the GPL
> only covers the code not the patent.
>
> > 2. It will need to be removed from Debian's tree -- at least moved to
> > non-free, yet as I said before, if Secure Computing is correct, SE-Linux
> is
> > not legal to use with GPL'd software anyway (at least the way I see it).
>
> Stuff that. I'm not putting this much work into non-free stuff! If the
> license gets changed to anything other than the GPL then I'll immediately
> cease work and file critical bug reports against ftp.debian.org asking for
> the packages to be removed. If Secure Computing want me to work on
material
>
> that's patented by them then they'll have to pay me at my usual consulting
> rates, plus back-pay for the last 6 months.
>
> > You'd better bet that GNU and other people who's code is being modified
to
> > work with SE-Linux will have ten purple cows on anyone who mixes
non-free
> > code with their GPLd code.
>
> The code can be still released as patches, but the problems of having them
> becoming obsolete and not matching the version your OS uses will remain.
>
> Basically I think that SE Linux is as good as dead for anything other than
> research use if this patent gets enforced.
>
> --
> I do not get viruses because I do not use MS software.
> If you use Outlook then please do not put my email address in your
> address-book so that WHEN you get a virus it won't use my address in the
> >From field.
>
> --
> You have received this message because you are subscribed to the selinux
> list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
> with
> the words "unsubscribe selinux" without quotes as the message.
>
> --
> You have received this message because you are subscribed to the selinux
list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
with
> the words "unsubscribe selinux" without quotes as the message.
>
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2002-06-05 1:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 22:28 Sorry, read this one: Re: SELinux Dumb Questions McFadden, Ken
2002-06-05 1:34 ` Admissions Office [this message]
2002-06-05 3:07 ` Russell Coker
2002-06-05 3:43 ` Admissions Office
2002-06-05 2:43 ` Outside observer comments Paul Wolfson
2002-06-05 3:14 ` Russell Coker
2002-06-05 4:07 ` JW
2002-06-05 4:28 ` Russell Coker
2002-06-05 7:29 ` Tom
2003-07-04 16:51 ` SE Linux & Education Ryan Emge
2002-06-07 6:28 ` Russell Coker
2002-06-05 7:26 ` Sorry, read this one: Re: SELinux Dumb Questions Tom
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 18:04 McFadden, Ken
2002-06-05 17:50 McFadden, Ken
2002-06-05 16:51 McFadden, Ken
2002-06-05 17:24 ` Tom
2002-06-05 20:07 ` Ben McGinnes
2002-06-06 19:25 ` David Caplan
2002-06-05 17:33 ` Justin Smith
2002-06-04 22:17 McFadden, Ken
2002-06-04 21:49 JW
2002-06-04 21:59 ` Admissions Office
2002-06-05 12:55 ` John Summerfield
2002-06-04 22:12 ` Russell Coker
2002-06-05 7:24 ` Tom
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='010001c20c31$1b799980$91c03b8e@OK' \
--to=admissions@internet.edu.nf \
--cc=carsten.grohmann@dr-baldeweg.de \
--cc=jw@centraltexasit.com \
--cc=ken.mcfadden@lmco.com \
--cc=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
--cc=tom_haigh@securecomputing.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.