All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaun Savage <savages@pcez.com>
To: SCC <SCC@securecomputing.com>
Cc: "'selinux@tycho.nsa.gov'" <selinux@tycho.nsa.gov>
Subject: Re: Message from Secure Computing
Date: Sat, 27 Jul 2002 06:22:54 -0700	[thread overview]
Message-ID: <3D429EAE.60906@pcez.com> (raw)
In-Reply-To: 7124107ACDA2D3118B7300A0C99D99A107DB53CB@stpntmx01.share.rsvl.securecomputing.com

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

One of the thing that conserns me is that if this "Assurance" is not 
legally challanged NOW.  That later action would be voided because it 
was not filed in a timely manner.   The contract that many people worked 
under, is that  SELinux code  IS GPLed and can be used in ANY  way, 
within the GPLed framework.   I see this "Assurance" issue as breach of 
contract for ANY body that has worked on SELinux without pay from SCC, 
for the good of the linux community and their self.

To me the "Assurance" is basicly worthless and I don't accept the new 
contract SCC is offering to the linux community.  Also I reserve the 
right to exersize my rights under the old contract, the use SELinux code 
in ANY GPL compliant project.

I have been unemployed for over a year. I have work on SELinux, for that 
year, to help the linux community by offering a RBAC os the the linux 
comunity. I also I want to use it in a commercial project that is 
released within the GPL framework.  By changing the contract, SCC have 
deprived me of the opertunity to offer a commercial product, released 
with in the GPL framework.  

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

iD8DBQE9Qp6in6I06Opz+XURAugmAKCxaP7wbpZdAAKi8MniZbf8YlExHwCgkiyQ
CSIhGJsepsAhfQ2hODmKY/o=
=iqst
-----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.

  parent reply	other threads:[~2002-07-27 13:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26 20:08 Message from Secure Computing SCC
2002-07-27  1:06 ` Shaun Savage
2002-07-27  6:57   ` Russell Coker
2002-07-27 13:22 ` Shaun Savage [this message]
2002-07-27 14:20   ` Russell Coker
2002-07-27 22:50     ` Dale Amon
2002-07-27 22:54     ` Dale Amon
2002-07-28  0:48       ` Russell Coker
2002-07-28  3:44     ` Brian May
2002-07-30  7:03   ` Tom
  -- strict thread matches above, loose matches on Subject: below --
2002-07-27 23:13 david kelman
2002-07-28  2:11 Westerman, Mark
2002-07-28  5:24 ` Edward J. Huff
2002-07-28  7:31   ` Brian May
2002-07-28  9:38     ` Edward J. Huff
2002-07-28 13:18   ` Russell Coker
2002-07-28 23:35     ` Edward J. Huff
2002-07-29  1:20       ` Edward J. Huff
2002-07-28 12:57 Westerman, Mark
2002-07-29  2:57 Shaun Savage

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=3D429EAE.60906@pcez.com \
    --to=savages@pcez.com \
    --cc=SCC@securecomputing.com \
    --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.