From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 03/15] Allow socket creation for imapd/pop3d communication
Date: Tue, 22 Mar 2011 08:44:49 -0400 [thread overview]
Message-ID: <4D8899C1.1090702@tresys.com> (raw)
In-Reply-To: <20110309210734.GA4670@siphos.be>
On 03/09/11 16:07, Sven Vermeulen wrote:
> During startup, authdaemon creates /var/lib/courier/authdaemon and creates
> a socket for communication with courier imapd and pop3d daemons
>
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> policy/modules/services/courier.te | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/policy/modules/services/courier.te b/policy/modules/services/courier.te
> index 55d64bc..877bab8 100644
> --- a/policy/modules/services/courier.te
> +++ b/policy/modules/services/courier.te
> @@ -52,7 +52,9 @@ allow courier_authdaemon_t courier_tcpd_t:fd use;
> allow courier_authdaemon_t courier_tcpd_t:tcp_socket rw_stream_socket_perms;
> allow courier_authdaemon_t courier_tcpd_t:fifo_file rw_file_perms;
>
> +manage_dirs_pattern(courier_authdaemon_t, courier_var_lib_t, courier_var_lib_t)
It sounds like this should be create_dirs_pattern instead.
> manage_sock_files_pattern(courier_authdaemon_t, courier_spool_t, courier_spool_t)
> +manage_sock_files_pattern(courier_authdaemon_t, courier_var_lib_t, courier_var_lib_t)
> files_search_spool(courier_authdaemon_t)
>
> corecmd_search_bin(courier_authdaemon_t)
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-03-22 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 21:07 [refpolicy] [PATCH 03/15] Allow socket creation for imapd/pop3d communication Sven Vermeulen
2011-03-22 12:44 ` Christopher J. PeBenito [this message]
2011-05-02 20:22 ` Sven Vermeulen
2011-05-04 13:13 ` 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=4D8899C1.1090702@tresys.com \
--to=cpebenito@tresys.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.