From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Joshua Brindle <jbrindle@tresys.com>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [RFC] 0/4 - Hierarchal apache policy for reference policy
Date: Thu, 18 Jan 2007 14:55:16 -0500 [thread overview]
Message-ID: <45AFD0A4.6020308@mentalrootkit.com> (raw)
In-Reply-To: <1169149203.22731.358.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Thu, 2007-01-18 at 13:40 -0500, Karl MacMillan wrote:
>> Joshua Brindle wrote:
>>> Karl MacMillan wrote:
>>>> Joshua Brindle wrote:
<snip>
>>>> 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?
>>>>
>>> nit: the meta-policy is short (5 lines). The policy itself is longer due
>>> to the propagation of rules to children types.
>>>
>> Fine - but that answer the question. Having to define container types
>> with a superset of the rules results in a much longer policy. I think
>> that it is going to be hard to convince people to add that policy.
>
> Policy build could automatically generate the rules for the container
> types from the child type rules, as long as they come from the same
> source (e.g. all part of the base policy build, or all within the same
> module). Then you only need to explicitly state rules for the container
> types for accesses that you wish to permit to externally defined
> children.
>
That's probably a good solution. Wouldn't be too hard to make a tool to
do this from selgen / sepolgen / madison.
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.
next prev parent reply other threads:[~2007-01-18 19:55 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
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 [this message]
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=45AFD0A4.6020308@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.