All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [RFC] 0/4 - Hierarchal apache policy for reference policy
Date: Thu, 18 Jan 2007 12:18:00 -0500	[thread overview]
Message-ID: <45AFABC8.2050101@mentalrootkit.com> (raw)
In-Reply-To: <45AFA08F.9080602@tresys.com>

Joshua Brindle wrote:
> This is an RFC for policy allowing management delegation through 
> hierarchical types.
> 
> Policy management often is handled by different administrators, based on 
> the application or applications that are being governed. As a result, 
> providing a means to delegate access to manage only certain aspects of 
> policy is desirable, and can be accomplished using hierarchical types.
> 
> The proof of concept apache policy module illustrates policy management 
> delegation through hierarchical types. This example apache policy works 
> together with an adds metapolicy to the apache module

It's good to see progress on this and a real fleshed-out example. I look 
forward to seeing the prototype policy server.

I think the biggest hurdle to this gaining widespread use is the length 
of the meta-policy, especially since it essentially repeats the policy 
for the sub-types. Any ideas about how to shorten this policy?

The other large issue, of course, is that this demonstrates how invasive 
the policy changes are in order to support delegation. This makes it 
very difficult for a policy admin to create a separate policy module 
that a) places hierarchical restrictions on a set of types and b) 
delegates administrative privileges to an admin type to make changes to 
those types.

My guess is that for real administrative roles to become viable in 
SELinux they are going to be largely site-defined in loadable modules 
(and the work at RH along those lines is using that as a starting 
assumption). So some way to support that seems necessary. At the very 
least I think that decoupling the hierarchical restrictions from the 
identifier names is needed. This also makes hierarchy work better with 
reference policy scoping.

Karl



--
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:[~2007-01-18 17:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 16:30 [RFC] 0/4 - Hierarchal apache policy for reference policy Joshua Brindle
2007-01-18 17:18 ` Karl MacMillan [this message]
2007-01-18 17:53   ` Joshua Brindle
2007-01-18 18:40     ` Karl MacMillan
2007-01-18 19:40       ` Stephen Smalley
2007-01-18 19:55         ` Karl MacMillan
2007-01-18 20:00           ` Joshua Brindle
2007-01-18 20:24             ` Stephen Smalley
2007-01-18 20:31               ` Stephen Smalley
2007-01-18 21:16               ` Joshua Brindle
2007-01-18 21:24                 ` Karl MacMillan
2007-01-18 21:44                   ` Joshua Brindle
2007-01-19 16:55                     ` Karl MacMillan
2007-01-25 21:17                       ` 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=45AFABC8.2050101@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.com \
    --cc=jbrindle@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.