All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: refpolicy roles / RBAC separation RFC
Date: Wed, 07 May 2008 13:32:26 -0400	[thread overview]
Message-ID: <1210181546.8778.20.camel@gorn> (raw)
In-Reply-To: <1209495402.25678.239.camel@moss-spartans.epoch.ncsc.mil>

On Tue, 2008-04-29 at 14:56 -0400, Stephen Smalley wrote:
> On Tue, 2008-04-29 at 11:54 -0400, Christopher J. PeBenito wrote:
> > Next we will be doing an experiment attempting to use the SELinux RBAC
> > functionality to separate users instead of SELinux TE.  What this means
> > is that the role field will start being used more substantially than it
> > currently is.  In a nutshell, this means that all user objects will have
> > the user's role rather than object_r.  Then the separate types will be
> > collapsed into one type where possible.  This will result in per-role
> > types (e.g., user_mozilla_t, staff_mozilla_t) collapsing too
> > (mozilla_t).
[...]
> > The above example rule utilizes a role attribute, which doesn't exist.
> > In the absence of role attributes, role dominance can be used, but its
> > unclear if the dominance code works, since no one uses it.

Turns out that I can't use role dominance because dom and domby in
constraints only seem to work (syntax error) between r1 and r2, rather
than r1 and a specific role.

> Yes, I think we should just add role attribute support.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150


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

  parent reply	other threads:[~2008-05-07 17:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 15:54 refpolicy roles / RBAC separation RFC Christopher J. PeBenito
2008-04-29 17:29 ` Daniel J Walsh
2008-04-29 19:20   ` Stephen Smalley
2008-04-30 12:18     ` Daniel J Walsh
2008-04-30 12:45       ` Stephen Smalley
2008-04-30 15:34         ` Daniel J Walsh
2008-04-30 17:17           ` Stephen Smalley
2008-04-30 17:35             ` Daniel J Walsh
2008-04-30 17:50               ` Stephen Smalley
2008-04-30 17:57                 ` Daniel J Walsh
2008-04-30 12:57       ` Stephen Smalley
2008-04-30 14:54         ` Christopher J. PeBenito
2008-04-29 18:56 ` Stephen Smalley
2008-04-29 19:34   ` Christopher J. PeBenito
2008-04-29 19:48     ` Stephen Smalley
2008-04-30 13:48       ` Christopher J. PeBenito
2008-04-30 14:05         ` Stephen Smalley
2008-04-30 14:51           ` Christopher J. PeBenito
2008-05-07 17:32   ` Christopher J. PeBenito [this message]
2008-05-07 18:07     ` 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=1210181546.8778.20.camel@gorn \
    --to=cpebenito@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --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.