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 1/1] Interface to allow reading of virus signature files.
Date: Sat, 27 Oct 2018 15:10:57 -0400 [thread overview]
Message-ID: <898ae270-1dcb-ee83-3c48-b243e3114f15@ieee.org> (raw)
In-Reply-To: <20181027161407.11324-1-dsugar@tresys.com>
On 10/27/2018 12:14 PM, David Sugar wrote:
> Signed-off-by: Dave Sugar <dsugar@tresys.com>
> ---
> policy/modules/services/clamav.if | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/policy/modules/services/clamav.if b/policy/modules/services/clamav.if
> index 7ad8e800..80ac5c1e 100644
> --- a/policy/modules/services/clamav.if
> +++ b/policy/modules/services/clamav.if
> @@ -177,6 +177,34 @@ interface(`clamav_read_state_clamd',`
> read_lnk_files_pattern($1, clamd_t, clamd_t)
> ')
>
> +#######################################
> +## <summary>
> +## Read clam virus signature files
> +## </summary>
> +## <desc>
> +## <p>
> +## Useful for when using things like 'sigtool'
> +## which provides useful information about
> +## ClamAV signature files.
> +## </p>
> +## </desc>
> +## <param name="domain">
> +## <summary>
> +## Domain allowed access.
> +## </summary>
> +## </param>
> +#
> +interface(`clamav_read_signatures',`
> + gen_require(`
> + type clamd_var_lib_t;
> + ')
> +
> + clamav_search_lib($1)
> + allow $1 clamd_var_lib_t:dir list_dir_perms;
> + read_files_pattern($1, clamd_var_lib_t, clamd_var_lib_t)
> + read_lnk_files_pattern($1, clamd_var_lib_t, clamd_var_lib_t)
> +')
> +
> ########################################
> ## <summary>
> ## All of the rules required to
Merged.
--
Chris PeBenito
prev parent reply other threads:[~2018-10-27 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 16:14 [PATCH 1/1] Interface to allow reading of virus signature files David Sugar
2018-10-27 19:10 ` 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=898ae270-1dcb-ee83-3c48-b243e3114f15@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).