All of lore.kernel.org
 help / color / mirror / Atom feed
From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 6/6] Courier IMAP needs to manage the users' maildir
Date: Tue, 30 Dec 2014 21:54:21 +0100	[thread overview]
Message-ID: <20141230205420.GC12724@bigboy.network2> (raw)
In-Reply-To: <1419970899-19892-7-git-send-email-sven.vermeulen@siphos.be>

On Tue, Dec 30, 2014 at 09:21:39PM +0100, Sven Vermeulen wrote:
> Without these permissions, the logon immediately terminates and the
> following shows up in the logs:
> 
> Dec 30 19:45:33 localhost imapd: Connection, ip=[::ffff:192.168.100.152]
> Dec 30 19:45:33 localhost imapd: chdir .maildir: Permission denied
> Dec 30 19:45:33 localhost imapd: root: Permission denied
> 
> The first denial (and many similar ones follow when granted):
> 
> type=AVC msg=audit(1419968733.163:197): avc:  denied  { search } for
> pid=4292 comm="courier-imapd" name=".maildir" dev="vda3" ino=393221
> scontext=system_u:system_r:courier_pop_t:s0
> tcontext=root:object_r:mail_home_rw_t:s0 tclass=dir
> 
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
>  courier.te | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/courier.te b/courier.te
> index c06c3ad..49fa11d 100644
> --- a/courier.te
> +++ b/courier.te
> @@ -148,6 +148,8 @@ corecmd_exec_shell(courier_pop_t)
>  
>  miscfiles_read_localization(courier_pop_t)
>  
> +mta_manage_mail_home_rw_content(courier_pop_t)
> +

Should this go together with a "mta_home_filetrans_mail_home(courier_pop_t, dir, ".maildir")", i.e. should courier-imapd be able to create that directory if it does not already exist?

>  userdom_manage_user_home_content_files(courier_pop_t)
>  userdom_manage_user_home_content_dirs(courier_pop_t)
>  

The above may, or may not, be redundant now that we have a .maildir with a private type

> -- 
> 2.0.5
> 
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy

-- 
Dominick Grift
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20141230/f8a76373/attachment-0001.bin 

  reply	other threads:[~2014-12-30 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 20:21 [refpolicy] [PATCH 0/6] Courier IMAPd related policy changes Sven Vermeulen
2014-12-30 20:21 ` [refpolicy] [PATCH 1/6] Courier TCPd startup creates imapd.pid.lock and imapd.lock Sven Vermeulen
2014-12-30 20:44   ` Dominick Grift
2014-12-30 20:21 ` [refpolicy] [PATCH 2/6] Locate authdaemon socket and communicate with authdaemon Sven Vermeulen
2014-12-30 20:47   ` Dominick Grift
2014-12-31 16:04     ` Sven Vermeulen
2014-12-30 20:21 ` [refpolicy] [PATCH 3/6] Allow authdaemon to access selinux fs to check SELinux state Sven Vermeulen
2014-12-30 20:21 ` [refpolicy] [PATCH 4/6] Grant setuid/setgid to courier_pop_t Sven Vermeulen
2014-12-30 20:21 ` [refpolicy] [PATCH 5/6] Execute courier helper script after authentication Sven Vermeulen
2014-12-30 20:21 ` [refpolicy] [PATCH 6/6] Courier IMAP needs to manage the users' maildir Sven Vermeulen
2014-12-30 20:54   ` Dominick Grift [this message]
2014-12-31 16:09     ` 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=20141230205420.GC12724@bigboy.network2 \
    --to=dac.override@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.