From: sven.vermeulen@siphos.be (Sven Vermeulen)
Date: Tue, 9 Apr 2013 22:27:53 +0200
Subject: [refpolicy] MCS Policy Constraints
In-Reply-To: <AC877EF0-952D-4C41-84A2-4FFBB84ED731@student.qut.edu.au>
References: <AC877EF0-952D-4C41-84A2-4FFBB84ED731@student.qut.edu.au>
Message-ID: <CAPzO=NzjeUC33aTrx8yBqrnZNoLO9a1KLQz-PQzDH2uXQuwb+w@mail.gmail.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

On Apr 9, 2013 10:11 PM, "Douglas Brown" <d46.brown@student.qut.edu.au>
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?

Isn't this because categories need to be set by users and this is only
possible on the (mainly) file classes?

Wkr,
  Sven Vermeulen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://oss.tresys.com/pipermail/refpolicy/attachments/20130409/ebd4e51e/attachment.html