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] Support pam_limits for inetd
Date: Wed, 8 Feb 2012 15:37:47 -0500	[thread overview]
Message-ID: <4F32DD1B.4040902@tresys.com> (raw)
In-Reply-To: <20111115095319.GA3117@siphos.be>

On 11/15/11 04:53, Sven Vermeulen wrote:
> The inetd daemon is PAM-aware and, given pam_limits, is able to set resource
> limits.
> 
> This patch grants it the sys_resource privilege as well as setrlimit.

Merged.

> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  inetd.te |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/inetd.te b/inetd.te
> index 6e82c4c..e341ab6 100644
> --- a/inetd.te
> +++ b/inetd.te
> @@ -38,9 +38,9 @@ ifdef(`enable_mcs',`
>  # Local policy
>  #
>  
> -allow inetd_t self:capability { setuid setgid };
> +allow inetd_t self:capability { setuid setgid sys_resource };
>  dontaudit inetd_t self:capability sys_tty_config;
> -allow inetd_t self:process { setsched setexec };
> +allow inetd_t self:process { setsched setexec setrlimit };
>  allow inetd_t self:fifo_file rw_fifo_file_perms;
>  allow inetd_t self:tcp_socket create_stream_socket_perms;
>  allow inetd_t self:udp_socket create_socket_perms;


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

      reply	other threads:[~2012-02-08 20:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  9:53 [refpolicy] [PATCH 1/1] Support pam_limits for inetd Sven Vermeulen
2012-02-08 20:37 ` 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=4F32DD1B.4040902@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.