From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: I am working to further shrink the size of policy in Fedora 17.
Date: Wed, 12 Oct 2011 09:40:16 -0400 [thread overview]
Message-ID: <4E9598C0.9080700@tresys.com> (raw)
In-Reply-To: <4E8F43CE.7010605@redhat.com>
On 10/07/11 14:24, Daniel J Walsh wrote:
> Right now, every domain that transitions to another domain gets the
> following rule written.
>
> dontaudit SOURCE TARGET : process { noatsecure siginh rlimitinh } ;
>
> In Fedora 17 policy right now we have 2152 rules, out of Dontaudit:
> 9415
>
>
> sesearch --dontaudit -p noatsecure | wc -l
> 2152
>
> We could rewrite this with one rule.
>
> dontaudit domain domain:process { noatsecure siginh rlimitinh } ;
>
> Of course this is more lenient then what we have now, although since
> it is dontaudit rules, not sure it matters.
>
> Comments?
I'm on the fence. On one hand, I hate to overspecify the policy, but on the other hand, these perms can only be hit on a domain transition. How much does this save?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
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:[~2011-10-12 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 18:24 I am working to further shrink the size of policy in Fedora 17 Daniel J Walsh
2011-10-12 13:40 ` Christopher J. PeBenito [this message]
2011-10-12 14:15 ` Daniel J Walsh
2011-10-12 17:37 ` Christopher J. PeBenito
2011-10-12 18:10 ` Daniel J Walsh
2011-10-12 18:45 ` Christopher J. PeBenito
2011-10-12 18:50 ` Daniel J Walsh
2011-10-12 19:06 ` 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=4E9598C0.9080700@tresys.com \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--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.