All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <domg472@gmail.com>
To: Sebastian Pfaff <sebastian.pfaff@gmail.com>
Cc: selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: request for review of, and collaboration on SELinux models wiki entry
Date: Thu, 02 Jul 2009 17:49:48 +0200	[thread overview]
Message-ID: <1246549788.26320.42.camel@notebook2.grift.internal> (raw)
In-Reply-To: <7DB3E8B4-9FFF-4FE1-873D-1A99C6EEF0AA@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1818 bytes --]

On Thu, 2009-07-02 at 17:25 +0200, Sebastian Pfaff wrote:
> hello,
> 
> from http://selinuxproject.org/page/SELinux_models (Multi Category  
> Security):
> 
> [...] Multi Category Security and Multi Level Security are mutually  
> exclusive.
> 
> > - MCS and MLS are just particular configurations of constraints for  
> > the
> > MLS engine and thus share the same field and engine logic.  MCS was an
> > attempt to make the MLS field and engine useful for general users, and
> > is being leveraged by sandbox and by svirt for separating multiple
> > instances of sandboxes or guest VMs.
> 
> In other words: MCS and MLS are not mutally exclusiv?! Not in SELinux  
> and not in gernal? For me, MCS in SELinux is an "extra",  which  you  
> can use with MLS (or MLS engine) at the same time. Please correct me,  
> if i'm wrong.
> 
> Imho, MCS uses "compartments" or categories to realize the need to  
> know principle and MLS uses vertical levels to achieve (at least in  
> SELinux) confidentiality (BLP model). Imo compartments and levels are  
> not mutally exclusive.

MCS and MLS are SELinux models (MCS and MLS are just particular
configurations of constraints for the MLS engine and thus share the same
field and engine logic.)

The MCS configuration of constraints conflict with the MLS configuration
of constraints.

In MCS the usage of assigned compartments is to the discretion of the
user

In MLS the usage of assigned compartments is mandatory.

As far as i know MCS and MLS are mutually exclusive. 

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

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-02 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 13:40 request for review of, and collaboration on SELinux models wiki entry Dominick Grift
2009-07-02 13:57 ` Stephen Smalley
2009-07-02 14:29 ` Stephen Smalley
2009-07-02 14:54   ` Dominick Grift
2009-07-02 15:04     ` Stephen Smalley
2009-07-02 16:26     ` Joshua Kramer
2009-07-02 15:36       ` Dominick Grift
2009-07-02 15:25   ` Sebastian Pfaff
2009-07-02 15:49     ` Dominick Grift [this message]
2009-07-02 17:03       ` Stephen Smalley
2009-07-02 18:12         ` Sebastian Pfaff
2009-07-06 12:42           ` Stephen Smalley

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=1246549788.26320.42.camel@notebook2.grift.internal \
    --to=domg472@gmail.com \
    --cc=sds@tycho.nsa.gov \
    --cc=sebastian.pfaff@gmail.com \
    --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.