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 1/1] Allow ping to get/set capabilities
Date: Thu, 26 Sep 2013 10:49:07 -0400	[thread overview]
Message-ID: <52444963.8070207@tresys.com> (raw)
In-Reply-To: <20130925182734.GB5287@siphos.be>

On Wed 25 Sep 2013 02:27:34 PM EDT, Sven Vermeulen wrote:
> When ping is installed with capabilities instead of being marked setuid,
> then the ping_t domain needs to be allowed to getcap/setcap.
>
> Reported-by: Luis Ressel <aranea@aixah.de>
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/modules/admin/netutils.te | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/policy/modules/admin/netutils.te b/policy/modules/admin/netutils.te
> index 557da97..cfe036a 100644
> --- a/policy/modules/admin/netutils.te
> +++ b/policy/modules/admin/netutils.te
> @@ -106,6 +106,8 @@ optional_policy(`
>  #
>
>  allow ping_t self:capability { setuid net_raw };
> +# When ping is installed with capabilities instead of setuid
> +allow ping_t self:process { getcap setcap };
>  dontaudit ping_t self:capability sys_tty_config;
>  allow ping_t self:tcp_socket create_socket_perms;
>  allow ping_t self:rawip_socket { create ioctl read write bind getopt setopt };

Merged.

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

      reply	other threads:[~2013-09-26 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 18:27 [refpolicy] [PATCH 1/1] Allow ping to get/set capabilities Sven Vermeulen
2013-09-26 14:49 ` 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=52444963.8070207@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.