All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Savage <savages@pcez.com>
To: Russell Coker <russell@coker.com.au>
Cc: selinux@tycho.nsa.gov
Subject: Re: A 'Statement of Assurance' on SELinux patents
Date: Tue, 06 Aug 2002 08:47:58 -0700	[thread overview]
Message-ID: <3D4FEFAE.2010308@pcez.com> (raw)
In-Reply-To: 20020806141841.8278925D@lyta.coker.com.au

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have retained an law firm to handle this issue for me.   I stated I 
was releasing a firewall, router based on NSA SELinux mid in 2001, 
before  the "assurance" came out.  The product is GPL complient, all 
source is avaiable, except for the configuration software, cacheing DNS, 
web/SOAP server, and snort alert anaysis program.  I plan to releases it 
for use in small school districts and advance home users.  I have even 
released the Compressed Block Device (CBD) driver GPL, It reduces the 
system size so that I can fix the whole system into 8M flash.  I have 
spent a year working on this project.

Shaun


Russell Coker wrote:

|On Tue, 6 Aug 2002 15:12, Ed Street wrote:
|
|>Well that's logical.  If you sell the rights to something you no longer
|>have control over the licensing of that product.
|
|
|No.  It is quite possible to sell things and keep control.  SCC can sell a
|product containing their patented code while keeping control over the 
patent,
|so it is just as easy for them to sell the patent while excluding certain
|types of use.
|
|>BTW has anyone
|>actually attempted to purchase the patent that applies to Selinux?  All
|>that would be needed is to purchase the rights to use it in Selinux but
|>not the complete patent.
|
|
|Who would want to do that?  The NSA appear to believe that they have 
already
|paid for all necessary rights, so naturally they will not want to pay twice
|(also such a payment would be regarded as an admission of guilt).
|
|I won't give SCC a cent, will you?
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - savages@savages.net

iD8DBQE9T++Wn6I06Opz+XURAj+TAKCvI0GmCMNvEZsKQhCNrJN3CpG1IACdEc16
n4ldioVaJfuyHpOyJ8XjwjU=
=HYHP
-----END PGP SIGNATURE-----



--
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.

  reply	other threads:[~2002-08-06 15:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06  1:35 A 'Statement of Assurance' on SELinux patents Erich Allewohl
2002-08-06  3:48 ` Ed Street
2002-08-06 13:02   ` Russell Coker
2002-08-06 13:12     ` Ed Street
2002-08-06 14:15       ` Dale Amon
2002-08-06 14:32         ` Ed Street
2002-08-06 14:18       ` Russell Coker
2002-08-06 15:47         ` Shaun Savage [this message]
2002-08-07  3:21         ` Ben McGinnes
2002-08-07 12:38           ` James Griffin
2002-08-07 19:56             ` JW
2002-08-08 13:53             ` Ben McGinnes
2002-08-08 14:22               ` Russell Coker
2002-08-08 14:40                 ` Joshua D. Guttman
2002-08-08 19:08                   ` Edward J. Huff
2002-08-10  0:31                 ` Ben McGinnes
2002-08-09  1:36               ` Rik van Riel
2002-08-06 12:57 ` Russell Coker

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=3D4FEFAE.2010308@pcez.com \
    --to=savages@pcez.com \
    --cc=russell@coker.com.au \
    --cc=selinux@tycho.nsa.gov \
    /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.