From: Joshua Brindle <method@manicmethod.com>
To: russell@coker.com.au
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
SE-Linux <selinux@tycho.nsa.gov>,
Karl MacMillan <kmacmillan@mentalrootkit.com>
Subject: Re: checkmodule and MLS/MCS support
Date: Mon, 15 Oct 2007 19:19:10 -0400 [thread overview]
Message-ID: <4713F56E.50002@manicmethod.com> (raw)
In-Reply-To: <200710160827.06055.russell@coker.com.au>
Russell Coker wrote:
> On Tuesday 16 October 2007 05:35, "Christopher J. PeBenito"
> <cpebenito@tresys.com> wrote:
>
>> If we're willing to say that non-refpolicy
>> building is a tiny minority/corner case, then this results in
>> practically no gain, since the compiler option is already taken care of
>> by the refpolicy build infrastructure.
>>
>
> This discussion started when I cited an example of a new SE Linux user who
> experienced great frustration due to the current mode of operation.
>
> If we have some new users who decide that this is difficult enough that
> selinux=0 is the solution then solving the problem has some real benefits.
>
This is pretty extreme, its just a flag.
--
This message was distributed to subscribers of the selinux mailing 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:[~2007-10-15 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 12:06 checkmodule and MLS/MCS support Russell Coker
2007-10-14 18:52 ` Joshua Brindle
2007-10-15 13:57 ` Stephen Smalley
2007-10-15 19:35 ` Christopher J. PeBenito
2007-10-15 22:27 ` Russell Coker
2007-10-15 23:19 ` Joshua Brindle [this message]
2007-10-16 0:39 ` Russell Coker
2007-10-16 12:10 ` Stephen Smalley
2007-10-16 12:43 ` Karl MacMillan
2007-10-16 12:51 ` Stephen Smalley
2007-10-16 13:22 ` Karl MacMillan
2007-10-16 13:42 ` Russell Coker
2007-10-15 14:42 ` 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=4713F56E.50002@manicmethod.com \
--to=method@manicmethod.com \
--cc=cpebenito@tresys.com \
--cc=kmacmillan@mentalrootkit.com \
--cc=russell@coker.com.au \
--cc=sds@tycho.nsa.gov \
--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.