From: Chris PeBenito <pebenito@ieee.org>
To: "Sugar, David" <dsugar@tresys.com>,
"selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH] Add interface to get status of rsyslog service
Date: Tue, 19 Feb 2019 19:32:05 -0800 [thread overview]
Message-ID: <b5ce162eabe7a64a5b610d3b4b9789bcf3cff6d1.camel@ieee.org> (raw)
In-Reply-To: <20190218200017.4439-1-dsugar@tresys.com>
On Mon, 2019-02-18 at 20:00 +0000, Sugar, David wrote:
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
> policy/modules/system/logging.if | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/policy/modules/system/logging.if
> b/policy/modules/system/logging.if
> index 16091eb6..21ec6501 100644
> --- a/policy/modules/system/logging.if
> +++ b/policy/modules/system/logging.if
> @@ -1222,6 +1222,25 @@ interface(`logging_admin_audit',`
> dontaudit $1 auditd_log_t:file map;
> ')
>
> +########################################
> +## <summary>
> +## Allow specified domain to check status of syslog unit
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +#
> +interface(`logging_status_syslog',`
> + gen_require(`
> + type syslogd_unit_t;
> + class service status;
> + ')
> +
> + allow $1 syslogd_unit_t:service status;
> +')
> +
> ########################################
> ## <summary>
> ## All of the rules required to administrate
This should be up after logging_domtrans_syslog().
--
Chris PeBenito
prev parent reply other threads:[~2019-02-20 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 20:00 [PATCH] Add interface to get status of rsyslog service Sugar, David
2019-02-18 20:00 ` [PATCH] Add interface to run cdrecord in caller domain Sugar, David
2019-02-20 3:31 ` Chris PeBenito
2019-02-20 3:32 ` Chris 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=b5ce162eabe7a64a5b610d3b4b9789bcf3cff6d1.camel@ieee.org \
--to=pebenito@ieee.org \
--cc=dsugar@tresys.com \
--cc=selinux-refpolicy@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).