From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] MCS Policy Constraints
Date: Wed, 10 Apr 2013 08:48:21 -0400 [thread overview]
Message-ID: <51655F95.50800@tresys.com> (raw)
In-Reply-To: <AC877EF0-952D-4C41-84A2-4FFBB84ED731@student.qut.edu.au>
On 04/09/13 16:10, Douglas Brown wrote:
> Hi all,
>
> The MCS policy has only file, database and one network-related class constraint. I'm sure this is deliberate by design, however I'd like to know if there's any impediment to adding category domain separation for all the classes in the MLS policy to the MCS policy and if I may submit a patch to do so?
There isn't a problem adding constraints to the other object classes. However, the MCS policy is intended by design to be simple and only cover files and DB, so the patch would not be accepted. If you're looking for comprehensive object class coverage with MCS, it might be sufficient to use the MLS policy but configure it with only 1 sensitivity (set MLS_SENS in build.conf).
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2013-04-10 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 20:10 [refpolicy] MCS Policy Constraints Douglas Brown
2013-04-09 20:27 ` Sven Vermeulen
2013-04-10 9:25 ` Douglas Brown
2013-04-10 12:48 ` Christopher J. PeBenito [this message]
2013-04-10 13:53 ` 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=51655F95.50800@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.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.