From: Chris PeBenito <pebenito@ieee.org>
To: David Sugar <dsugar@tresys.com>,
"selinux-refpolicy@vger.kernel.org"
<selinux-refpolicy@vger.kernel.org>
Subject: Re: [PATCH] Interface to read cron_system_spool_t
Date: Sat, 17 Nov 2018 18:54:17 -0500 [thread overview]
Message-ID: <d2075460-b361-68f6-3d1e-b95e8b78367d@ieee.org> (raw)
In-Reply-To: <20181116174221.1254-1-dsugar@tresys.com>
On 11/16/18 12:43 PM, David Sugar wrote:
> Useful for the case that manage isn't requied.
>
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
> policy/modules/services/cron.if | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/policy/modules/services/cron.if b/policy/modules/services/cron.if
> index d40848ab..3278c216 100644
> --- a/policy/modules/services/cron.if
> +++ b/policy/modules/services/cron.if
> @@ -706,6 +706,26 @@ interface(`cron_manage_system_spool',`
> manage_files_pattern($1, system_cron_spool_t, system_cron_spool_t)
> ')
>
> +########################################
> +## <summary>
> +## Read the system spool.
> +## </summary>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +#
> +interface(`cron_read_system_spool',`
> + gen_require(`
> + type system_cron_spool_t;
> + ')
> +
> + cron_search_spool($1)
> + list_dirs_pattern($1, system_cron_spool_t, system_cron_spool_t)
> + read_files_pattern($1, system_cron_spool_t, system_cron_spool_t)
> +')
> +
> ########################################
> ## <summary>
> ## Read and write crond temporary files.
Merged.
--
Chris PeBenito
prev parent reply other threads:[~2018-11-18 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 17:43 [PATCH] Interface to read cron_system_spool_t David Sugar
2018-11-17 23:54 ` 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=d2075460-b361-68f6-3d1e-b95e8b78367d@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).