From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 5/5] Allow initrc to manage asterisk log and pid file attributes
Date: Fri, 20 Apr 2012 16:37:46 -0400 [thread overview]
Message-ID: <4F91C91A.1060608@tresys.com> (raw)
In-Reply-To: <20120326185052.GF24792@siphos.be>
On 03/26/12 14:50, Sven Vermeulen wrote:
>
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> policy/modules/system/init.te | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/policy/modules/system/init.te b/policy/modules/system/init.te
> index b7fcbe3..dd37cf1 100644
> --- a/policy/modules/system/init.te
> +++ b/policy/modules/system/init.te
> @@ -571,6 +571,11 @@ optional_policy(`
> ')
>
> optional_policy(`
> + asterisk_setattr_logs(initrc_t)
> + asterisk_setattr_pid_files(initrc_t)
> +')
> +
> +optional_policy(`
> bind_read_config(initrc_t)
>
> # for chmod in start script
Merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2012-04-20 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 18:48 [refpolicy] [PATCH 0/5] Updates for asterisk domain Sven Vermeulen
2012-03-26 18:49 ` [refpolicy] [PATCH 1/5] Allow asterisk to chown its own /var/run/asterisk directory Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
2012-03-26 18:49 ` [refpolicy] [PATCH 2/5] Allow asterisk to listen on its control socket Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
2012-03-26 18:50 ` [refpolicy] [PATCH 3/5] Asterisk requires access to /dev/random too Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
2012-03-26 18:50 ` [refpolicy] [PATCH 4/5] Add interfaces to manage attributes of asterisk log and pid files Sven Vermeulen
2012-04-20 20:37 ` Christopher J. PeBenito
2012-03-26 18:50 ` [refpolicy] [PATCH 5/5] Allow initrc to manage asterisk log and pid file attributes Sven Vermeulen
2012-04-20 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=4F91C91A.1060608@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.