From: dominick.grift@gmail.com (grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/2] Allow syslogger to manage cron log files
Date: Tue, 27 Nov 2012 14:58:19 +0100 [thread overview]
Message-ID: <1354024699.1888.19.camel@localhost> (raw)
In-Reply-To: <1352566324-17831-2-git-send-email-sven.vermeulen@siphos.be>
On Sat, 2012-11-10 at 17:52 +0100, Sven Vermeulen wrote:
> Some cron daemons, including vixie-cron, support using the system logger for
> handling their logging events. Hence we allow syslogd_t to manage the cron logs,
> and put a file transition in place for the system logger when it creates the
> cron.log file.
>
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> policy/modules/system/logging.te | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/policy/modules/system/logging.te b/policy/modules/system/logging.te
> index 72d67ad..091db87 100644
> --- a/policy/modules/system/logging.te
> +++ b/policy/modules/system/logging.te
> @@ -490,6 +490,11 @@ optional_policy(`
> ')
>
> optional_policy(`
> + cron_manage_log(syslogd_t)
There is a cron_manage_log_files()
> + cron_generic_log_filetrans_log(syslogd_t, file, "cron.log")
> +')
> +
> +optional_policy(`
> inn_manage_log(syslogd_t)
> ')
>
next prev parent reply other threads:[~2012-11-27 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 16:52 [refpolicy] [PATCH 0/2] Smaller updates on main policy modules Sven Vermeulen
2012-11-10 16:52 ` [refpolicy] [PATCH 1/2] Allow syslogger to manage cron log files Sven Vermeulen
2012-11-27 13:58 ` grift [this message]
2012-11-10 16:52 ` [refpolicy] [PATCH 2/2] Run ipset in iptables domain Sven Vermeulen
2012-11-27 13:37 ` [refpolicy] [PATCH 0/2] Smaller updates on main policy modules Christopher J. PeBenito
2012-11-27 13:40 ` Christopher J. PeBenito
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=1354024699.1888.19.camel@localhost \
--to=dominick.grift@gmail.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.