From: dominick.grift@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/2] Grant write privileges to squid on its log files
Date: Fri, 16 Aug 2013 13:30:33 +0200 [thread overview]
Message-ID: <1376652633.3531.3.camel@d30> (raw)
In-Reply-To: <1376634106-16328-2-git-send-email-sven.vermeulen@siphos.be>
On Fri, 2013-08-16 at 08:21 +0200, Sven Vermeulen wrote:
> The squid daemon currently seems to require write privileges on the files
> (squid_log_t) - append no longer cuts it. This is confirmed for both the
> cache.log file as well as the netdb.state file.
Merged with changes, thanks
You might as well use a single manage_files_pattern now
>
> Switching append_files_pattern to write_files_pattern.
>
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> squid.te | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/squid.te b/squid.te
> index 991d7ea..ae41c6c 100644
> --- a/squid.te
> +++ b/squid.te
> @@ -74,7 +74,7 @@ allow squid_t squid_conf_t:file read_file_perms;
> allow squid_t squid_conf_t:lnk_file read_lnk_file_perms;
>
> manage_dirs_pattern(squid_t, squid_log_t, squid_log_t)
> -append_files_pattern(squid_t, squid_log_t, squid_log_t)
> +write_files_pattern(squid_t, squid_log_t, squid_log_t)
> create_files_pattern(squid_t, squid_log_t, squid_log_t)
> setattr_files_pattern(squid_t, squid_log_t, squid_log_t)
> manage_lnk_files_pattern(squid_t, squid_log_t, squid_log_t)
next prev parent reply other threads:[~2013-08-16 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 6:21 [refpolicy] [PATCH 0/2] Few contrib updates Sven Vermeulen
2013-08-16 6:21 ` [refpolicy] [PATCH 1/2] Grant write privileges to squid on its log files Sven Vermeulen
2013-08-16 11:30 ` Dominick Grift [this message]
2013-08-16 6:21 ` [refpolicy] [PATCH 2/2] Use nscd socket for webalizer Sven Vermeulen
2013-08-16 11:20 ` Dominick Grift
2013-08-17 8:24 ` Sven Vermeulen
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=1376652633.3531.3.camel@d30 \
--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.