From: Michael C Thompson <thompsmc@us.ibm.com>
To: Chris PeBenito <pebenito@gentoo.org>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Default Mikefile in /usr/share/selinux/devel not nice
Date: Mon, 02 Oct 2006 10:20:25 -0500 [thread overview]
Message-ID: <45212E39.9080105@us.ibm.com> (raw)
In-Reply-To: <1159590751.12161.10.camel@gorn.pebenito.net>
Chris PeBenito wrote:
> On Fri, 2006-09-29 at 16:12 -0500, Michael C Thompson wrote:
>> I just discovered a nasty surprise waiting for me in the default
>> Makefile provided by selinux-policy-devel.
>>
>> Basically, the Makefile produces, on an MLS system, a TYPE value of
>> mls-msc (this is due to the SELINUXTYPE=mls line in
>> /etc/selinux/config). This will not 'enable_mls' for the M4FLAGS,
>> because the Makefile in /usr/share/selinux/devel/include/ does a
>> findstring for '-mls'.
>>
>> Dan Walsh has suggested a fix for the default Makefile, but I'm
>> wondering why we can't just change
>> /usr/share/selinux/devel/include/Makefile to do a $(findstring
>> mls,$TYPE)) instead, since its not unreasonable to think that TYPE=mls
>> makes sense.
>
> There is some confusion here, the SELINUXTYPE is not the same as TYPE in
> refpolicy, it is NAME in refpolicy. The TYPE of the Redhat MLS policy
> is strict-mls. TYPE=mls does not make sense, since it does not specify
> if the policy is strict or targeted.
Are there flags (like 'enable_mls') in the policy which require this
delineation?
Mike
--
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:[~2006-10-02 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 21:12 Default Mikefile in /usr/share/selinux/devel not nice Michael C Thompson
2006-09-30 4:32 ` Chris PeBenito
2006-10-02 15:20 ` Michael C Thompson [this message]
2006-10-02 15:33 ` Christopher J. PeBenito
2006-10-02 20:47 ` Daniel J Walsh
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=45212E39.9080105@us.ibm.com \
--to=thompsmc@us.ibm.com \
--cc=pebenito@gentoo.org \
--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.