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 getsched for syslog-ng
Date: Fri, 4 May 2012 10:41:07 -0400	[thread overview]
Message-ID: <4FA3EA83.9070902@tresys.com> (raw)
In-Reply-To: <20120501081313.GH32060@siphos.be>

On 05/01/12 04:13, Sven Vermeulen wrote:
> Recent syslog-ng implementation uses a threading library that requires the getsched permission.
> 
> See also https://bugs.gentoo.org/show_bug.cgi?id=405425
> 
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  policy/modules/system/logging.te |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/policy/modules/system/logging.te b/policy/modules/system/logging.te
> index ebc216c..6bf2058 100644
> --- a/policy/modules/system/logging.te
> +++ b/policy/modules/system/logging.te
> @@ -358,7 +358,8 @@ allow syslogd_t self:capability { dac_override sys_resource sys_tty_config net_a
>  dontaudit syslogd_t self:capability sys_tty_config;
>  # setpgid for metalog
>  # setrlimit for syslog-ng
> -allow syslogd_t self:process { signal_perms setpgid setrlimit };
> +# getsched for syslog-ng
> +allow syslogd_t self:process { signal_perms setpgid setrlimit getsched };
>  # receive messages to be logged
>  allow syslogd_t self:unix_dgram_socket create_socket_perms;
>  allow syslogd_t self:unix_stream_socket create_stream_socket_perms;

Merged.

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

      reply	other threads:[~2012-05-04 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01  8:13 [refpolicy] [PATCH 1/1] Allow getsched for syslog-ng Sven Vermeulen
2012-05-04 14:41 ` 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=4FA3EA83.9070902@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.