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] Grant ping_t getattr on rawip_socket
Date: Mon, 18 Aug 2014 09:49:55 -0400	[thread overview]
Message-ID: <53F20483.4060107@tresys.com> (raw)
In-Reply-To: <1403817727-15799-1-git-send-email-aranea@aixah.de>

On 6/26/2014 5:22 PM, Luis Ressel wrote:
> If the (sadly nearly undocumented) Linux kernel feature which allows
> specific user groups to send ICMP echos without CAP_NET_RAW
> (configurable with the sysctl net.ipv4.ping_group_range, available since
> 3.0) is used, ping needs the getattr permission of the rawip_socket
> class in order to work.
> ---
>  policy/modules/admin/netutils.te | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/policy/modules/admin/netutils.te b/policy/modules/admin/netutils.te
> index 7aa7384..570bf2c 100644
> --- a/policy/modules/admin/netutils.te
> +++ b/policy/modules/admin/netutils.te
> @@ -110,7 +110,7 @@ allow ping_t self:capability { setuid net_raw };
>  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 };
> +allow ping_t self:rawip_socket { create ioctl read write bind getopt setopt getattr };
>  allow ping_t self:packet_socket { create ioctl read write bind getopt setopt };
>  allow ping_t self:netlink_route_socket create_netlink_socket_perms;

Merged.

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

      parent reply	other threads:[~2014-08-18 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 21:22 [refpolicy] [PATCH] Grant ping_t getattr on rawip_socket Luis Ressel
2014-08-11 12:33 ` Luis Ressel
2014-08-18 13: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=53F20483.4060107@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.