All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/4] Allow portage to set file capabilities, needed for installations like for wireshark
Date: Mon, 02 May 2011 11:30:53 -0400	[thread overview]
Message-ID: <4DBECE2D.4040302@tresys.com> (raw)
In-Reply-To: <20110428193012.GB29963@siphos.be>

On 04/28/11 15:30, Sven Vermeulen wrote:
> The installation of the wireshark package (and perhaps others) requires
> portage setting file capabilities (through the setcap binary).

Merged.

> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/modules/admin/portage.te |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/policy/modules/admin/portage.te b/policy/modules/admin/portage.te
> index 8f41c2e..d6697d3 100644
> --- a/policy/modules/admin/portage.te
> +++ b/policy/modules/admin/portage.te
> @@ -125,7 +125,7 @@ optional_policy(`
>  # - setexec to run portage fetch
>  allow portage_t self:process { setfscreate setexec };
>  # - kill for mysql merging, at least
> -allow portage_t self:capability { sys_nice kill };
> +allow portage_t self:capability { sys_nice kill setfcap };
>  
>  # user post-sync scripts
>  can_exec(portage_t, portage_conf_t)


-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

      reply	other threads:[~2011-05-02 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 19:30 [refpolicy] [PATCH 2/4] Allow portage to set file capabilities, needed for installations like for wireshark Sven Vermeulen
2011-05-02 15:30 ` Christopher J. PeBenito [this message]

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=4DBECE2D.4040302@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.