All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Faden <Glenn.Faden@sun.com>
To: rob myers <rob.myers@gtri.gatech.edu>
Cc: "selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: Not quite MLS.
Date: Mon, 17 Aug 2009 17:40:24 -0700	[thread overview]
Message-ID: <4A89F878.1040604@sun.com> (raw)
In-Reply-To: <1250545104.3588.149.camel@rxm-581b.stl.gtri.gatech.edu>

rob myers wrote:
>
> I believe the difference between SELinux with MLS policy and what I am
> trying to build is that I want higher sensitivity levels to dominate
> lower sensitivity levels only on a per category basis.
>
> For example, it is my understanding that under MLS UserB must have
> sensitivity level 3 access to category 3 because UserB has access to
> sensitivity level 3 access to other categories.  Another possibility
> under MLS would be to remove UserB's access to category 3 for all
> sensitivities.  Neither of these is what I want the system to do.
>   
For MLS systems based on the Mitre/DIA label encodings format it is 
possible to exclude specific categories on a per sensitivity label basis 
from the User Accreditation Range. For an example, see:

    http://docs.sun.com/app/docs/doc/819-0874/sec6-2?a=view

In your example, you could define specify the valid categories for each 
of the four classifications (levels).

    UserA's access matrix:

    category, sl0, sl1, sl2, sl3
           0, yes, yes, no , no 
           1, yes, yes, no , no 
           2, yes, yes, yes, no 
           3, yes, yes, yes, yes 


    UserB's access matrix:

    category, sl0, sl1, sl2, sl3
           0, yes, yes, yes, yes
           1, yes, yes, yes, yes
           2, yes, yes, yes, yes
           3, yes, yes, yes, no 


you could specify

    classification= s10; all compartment combinations valid;
    classification= s11; all compartment combinations valid;
    classification= s12; all compartment combinations valid except:
    c0
    c1
    classification= s13; only valid compartment combinations:
    c3


So it is possible to specify a User Accreditation Range conforming to 
either the UserA or UserB matrix. However, the format only provides for 
a single User Accreditiation Range that would apply to all users. In MLS 
systems I'm familiar with, there is no facility to exclude categories 
from the kernel dominance checks.

--Glenn

--
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:[~2009-08-18  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-14 21:30 Not quite MLS rob myers
2009-08-17 11:40 ` Stephen Smalley
2009-08-17 21:38   ` rob myers
2009-08-18  0:40     ` Glenn Faden [this message]
2009-08-18 14:19       ` rob myers
2009-08-18 16:15       ` Paul McNabb
2009-08-19 21:53         ` Casey Schaufler
2009-08-18 14:34     ` 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=4A89F878.1040604@sun.com \
    --to=glenn.faden@sun.com \
    --cc=rob.myers@gtri.gatech.edu \
    --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.