From: dominick.grift@gmail.com (grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 01/11] Moving sandbox code to sandbox section (v2)
Date: Sun, 09 Dec 2012 14:51:22 +0100 [thread overview]
Message-ID: <1355061082.1797.65.camel@localhost> (raw)
In-Reply-To: <1355000222-7297-2-git-send-email-sven.vermeulen@siphos.be>
On Sat, 2012-12-08 at 21:56 +0100, Sven Vermeulen wrote:
> Some portage_sandbox_t code is sitting in the main portage_t section. Moving
> this to its own sandbox location. Also switch a domain_trans towards
> spec_domtrans_pattern as this cleans the policy up a little bit.
>
This was merged, thanks
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> portage.te | 13 +++++--------
> 1 files changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/portage.te b/portage.te
> index 7d2fc08..f9b9ce8 100644
> --- a/portage.te
> +++ b/portage.te
> @@ -150,8 +150,7 @@ optional_policy(`
> #
>
> # - setfscreate for merging to live fs
> -# - setexec to run portage fetch
> -allow portage_t self:process { setfscreate setexec };
> +allow portage_t self:process { setfscreate };
> # - kill for mysql merging, at least
> allow portage_t self:capability { sys_nice kill setfcap };
> dontaudit portage_t self:capability { dac_read_search };
> @@ -174,13 +173,8 @@ allow portage_fetch_t portage_t:process sigchld;
> dontaudit portage_fetch_t portage_devpts_t:chr_file { read write };
>
> # transition to sandbox for compiling
> -domain_trans(portage_t, portage_exec_t, portage_sandbox_t)
> +spec_domtrans_pattern(portage_t, portage_exec_t, portage_sandbox_t)
> corecmd_shell_spec_domtrans(portage_t, portage_sandbox_t)
> -allow portage_sandbox_t portage_t:fd use;
> -allow portage_sandbox_t portage_t:fifo_file rw_fifo_file_perms;
> -allow portage_sandbox_t portage_t:process sigchld;
> -allow portage_sandbox_t self:process ptrace;
> -dontaudit portage_sandbox_t self:netlink_route_socket rw_netlink_socket_perms;
>
> # run scripts out of the build directory
> can_exec(portage_t, portage_tmp_t)
> @@ -338,6 +332,9 @@ optional_policy(`
> # - SELinux-enforced sandbox
> #
>
> +allow portage_sandbox_t self:process ptrace;
> +dontaudit portage_sandbox_t self:netlink_route_socket rw_netlink_socket_perms;
> +
> portage_compile_domain(portage_sandbox_t)
>
> auth_use_nsswitch(portage_sandbox_t)
next prev parent reply other threads:[~2012-12-09 13:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 20:56 [refpolicy] [PATCH 00/11] Contrib changes Sven Vermeulen
2012-12-08 20:56 ` [refpolicy] [PATCH 01/11] Moving sandbox code to sandbox section (v2) Sven Vermeulen
2012-12-09 13:51 ` grift [this message]
2012-12-08 20:56 ` [refpolicy] [PATCH 02/11] Allow sandbox to log violations Sven Vermeulen
2012-12-09 13:55 ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 03/11] Initial policy for logsentry Sven Vermeulen
2012-12-08 22:03 ` grift
2013-10-05 7:22 ` Dominick Grift
2012-12-08 20:56 ` [refpolicy] [PATCH 04/11] Initial policy for makewhatis Sven Vermeulen
2012-12-08 21:57 ` grift
2012-12-09 9:44 ` Sven Vermeulen
2012-12-09 10:59 ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 05/11] Use rw_fifo_file_perms Sven Vermeulen
2012-12-09 13:58 ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 06/11] Apache should not depend on gpg Sven Vermeulen
2012-12-09 13:59 ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 07/11] Mark make.profile entry as portage_conf_t Sven Vermeulen
2012-12-08 21:46 ` grift
2012-12-08 20:56 ` [refpolicy] [PATCH 08/11] Named init script creates rundir Sven Vermeulen
2012-12-09 14:00 ` grift
2012-12-08 20:57 ` [refpolicy] [PATCH 09/11] Add ~/.maildir as a valid maildir destination Sven Vermeulen
2012-12-09 14:01 ` grift
2012-12-08 20:57 ` [refpolicy] [PATCH 10/11] Support stunnel_read_config for startup Sven Vermeulen
2012-12-09 14:03 ` grift
2012-12-08 20:57 ` [refpolicy] [PATCH 11/11] Updates on stunnel policy Sven Vermeulen
2012-12-09 14:04 ` 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=1355061082.1797.65.camel@localhost \
--to=dominick.grift@gmail.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.