From: "Admissions Office" <admissions@internet.edu.nf>
To: "Greg KH" <greg@kroah.com>, "Crispin Cowan" <crispin@wirex.com>
Cc: <Valdis.Kletnieks@vt.edu>, "Russell Coker" <russell@coker.com.au>,
<jw@centraltexasit.com>, <selinux@tycho.nsa.gov>,
"Haigh, Tom" <tom_haigh@securecomputing.com>,
"Carsten Grohmann" <carsten.grohmann@dr-baldeweg.de>,
<linux-security-module@wirex.com>
Subject: Re: To confusing....
Date: Mon, 17 Jun 2002 10:41:26 -0600 [thread overview]
Message-ID: <001201c2161d$d378b0c0$eeb6b38e@OK> (raw)
In-Reply-To: 20020617163139.GF14164@kroah.com
Our company will not be using the SELinux for clients because, our
management has determined the situation is to confusing and will not place
our business at risk.
Pamela Patterson
OpenDNS Crop
--
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-17 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 16:11 SE-Linux on SuSE JW
2002-06-03 10:23 ` Carsten Grohmann
2002-06-03 14:50 ` SELinux Dumb Questions Admissions Office
2002-06-03 15:39 ` Russell Coker
2002-06-03 17:50 ` Mirror Offer Admissions Office
2002-06-03 18:45 ` Russell Coker
2002-06-03 19:10 ` Stephen Smalley
2002-06-03 19:16 ` Admissions Office
2002-06-04 21:30 ` SELinux Dumb Questions JW
2002-06-04 21:59 ` Russell Coker
2002-06-05 0:58 ` Dale Amon
[not found] ` <200206042255.g54MtHu1003846@turing-police.cc.vt.edu>
[not found] ` <3CFD49A6.5060400@wirex.com>
2002-06-05 3:52 ` SELinux to GPL or not to GPL Admissions Office
[not found] ` <20020617163139.GF14164@kroah.com>
2002-06-17 16:41 ` Admissions Office [this message]
2002-06-05 1:30 ` SELinux Dumb Questions Admissions Office
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='001201c2161d$d378b0c0$eeb6b38e@OK' \
--to=admissions@internet.edu.nf \
--cc=Valdis.Kletnieks@vt.edu \
--cc=carsten.grohmann@dr-baldeweg.de \
--cc=crispin@wirex.com \
--cc=greg@kroah.com \
--cc=jw@centraltexasit.com \
--cc=linux-security-module@wirex.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.