From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] removed the rw autofs stuff added nfs search for portage_t and allowed use of nsswitch
Date: Tue, 9 Oct 2012 10:09:33 -0400 [thread overview]
Message-ID: <5074301D.1040508@tresys.com> (raw)
In-Reply-To: <1349186357-19745-1-git-send-email-mthode@mthode.org>
On 10/02/12 09:59, Matthew Thode wrote:
> subject more or less speaks for itself, lessened the permissions needed from autofs and fixed a couple of AVC denials with grifts help in irc, thanks :D
>
> ---
> portage.te | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/portage.te b/portage.te
> index 128e7d6..321b1ac 100644
> --- a/portage.te
> +++ b/portage.te
> @@ -193,6 +193,8 @@ files_manage_all_files(portage_t)
> selinux_get_fs_mount(portage_t)
>
> auth_manage_shadow(portage_t)
> +auth_use_nsswitch(portage_fetch_t)
> +auth_use_nsswitch(portage_sandbox_t)
>
> # merging baselayout will need this:
> init_exec(portage_t)
[cut]
> @@ -321,6 +322,7 @@ ifdef(`hide_broken_symptoms',`
> ')
>
> tunable_policy(`portage_use_nfs',`
> + fs_getattr_nfs(portage_t)
> fs_getattr_nfs(portage_fetch_t)
> fs_manage_nfs_dirs(portage_fetch_t)
> fs_manage_nfs_files(portage_fetch_t)
The lines should go with the sections, i.e. the portage_fetch_t addition should go in the portage_fetch_t section, and the portage_sandbox_t addition should go in the portage_sandbox_t section.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-10-09 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 7:25 [refpolicy] [PATCH] added autofs support Matthew Thode
2012-10-02 8:55 ` Dominick Grift
2012-10-02 13:59 ` [refpolicy] [PATCH] removed the rw autofs stuff added nfs search for portage_t and allowed use of nsswitch Matthew Thode
2012-10-09 14:09 ` Christopher J. PeBenito [this message]
2012-10-09 15:03 ` Dominick Grift
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=5074301D.1040508@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.