From: Joshua Brindle <jbrindle@tresys.com>
To: SE Linux <selinux@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>
Subject: [RFC] 0/4 - Hierarchal apache policy for reference policy
Date: Thu, 18 Jan 2007 11:30:07 -0500 [thread overview]
Message-ID: <45AFA08F.9080602@tresys.com> (raw)
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 and adds a policy
server labeling file (apache.pc) that must be appended to the policy
context file (the default for policy server is
/etc/selinux/policy_contexts) to split apache’s policy management
between different users.
In this policy, for example, management access to apache content is
broken down hierarchically based on the content owner. Then
apache_t.user_content is labeled user_apache_policy_t to only allow
user_t to add new rules for apache_t.user_content type. Similar rules
prevent user_t from using types like apache_t.staff_content. See the end
of apache_per_role_template() in apache.if for the rules that govern how
users change policy.
The enforcement of the metapolicy requires the policy management server,
which will be released for preview soon.
--
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.
next reply other threads:[~2007-01-18 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 16:30 Joshua Brindle [this message]
2007-01-18 17:18 ` [RFC] 0/4 - Hierarchal apache policy for reference policy Karl MacMillan
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=45AFA08F.9080602@tresys.com \
--to=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.