All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Michael C Thompson <thompsmc@us.ibm.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: MLS + MCS?
Date: Thu, 02 Nov 2006 11:35:13 -0500	[thread overview]
Message-ID: <1162485313.18181.9.camel@sgc> (raw)
In-Reply-To: <454A134D.5060902@us.ibm.com>

On Thu, 2006-11-02 at 09:48 -0600, Michael C Thompson wrote:
> While writing some policy, I came across a situation that was causing 
> the policy I was writing to be constructed in an invalid fashion. What 
> was happening was this:
> 
> Using an old Makefile, my $(TYPE) was being generated as 
> 'strict-mls-mcs', which was causing the support template 'gen_context' 
> to get completely confused.
> 
> The macro is defined thusly:
[cut]
> I'm wondering, how does this make sense? I'm unclear as to how having 
> both mls_sensitivity and [mcs_catergories] defined in this way has meaning.
> 
> Because of having both '-mls' and '-mcs' in my $(TYPE), the invalid 
> policy I was compiling ended up looking like this:
> user:role:type:$2:s0:$3
> 
> It would seem to me that MLS and MCS are mutually exclusive, at least in 
> this macro.

Yes, they are mutually exclusive.  Sounds like the Makefile that redhat
has is making a mistake on setting TYPE; it has to figure out more than
the upstream refpolicy Makefiles need to because of the
redhat /usr/share/selinux/*/devel setup.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150


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

  reply	other threads:[~2006-11-02 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 15:48 MLS + MCS? Michael C Thompson
2006-11-02 16:35 ` Christopher J. PeBenito [this message]
2006-11-02 16:49   ` Michael C Thompson
2006-11-02 18:58     ` Christopher J. PeBenito

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=1162485313.18181.9.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=thompsmc@us.ibm.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.