From: russell@coker.com.au (Russell Coker)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] services_amavis.patch
Date: Tue, 7 Oct 2008 06:29:14 +1000 [thread overview]
Message-ID: <200810070729.16636.russell@coker.com.au> (raw)
In-Reply-To: <1223317216.2165.35.camel@gorn>
On Tuesday 07 October 2008 05:20, "Christopher J. PeBenito"
<cpebenito@tresys.com> wrote:
> One thing specific example that I noticed recently about these was that
> there is a mail_spool_t in mta, and postfix and qmail also have their
> own spool types. ?Those sounded like they could possibly all merge into
> mail_spool_t, but I haven't had a chance to investigate further.
The mail_spool_t in mta.te is for /var/spool/mail - this is fully accessible
to users.
The spool directories for the mail servers have limited access for users.
So there is some possibility for type sharing, but /var/spool/mail should not
share a type with /var/spool/postfix.
--
russell at coker.com.au
http://etbe.coker.com.au/ My Blog
http://www.coker.com.au/sponsorship.html Sponsoring Free Software development
next prev parent reply other threads:[~2008-10-06 20:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-24 20:52 [refpolicy] services_amavis.patch Daniel J Walsh
2008-09-25 7:19 ` Russell Coker
2008-09-25 12:19 ` Martin Orr
2008-09-27 0:42 ` Russell Coker
2008-10-01 11:17 ` Martin Orr
2008-10-01 12:31 ` Daniel J Walsh
2008-10-02 2:32 ` Russell Coker
2008-10-06 18:28 ` Christopher J. PeBenito
2008-10-02 12:31 ` Christopher J. PeBenito
2008-10-02 20:29 ` Russell Coker
2008-09-25 20:10 ` Daniel J Walsh
2008-09-25 21:03 ` Russell Coker
2008-10-06 18:20 ` Christopher J. PeBenito
2008-10-06 20:29 ` Russell Coker [this message]
2008-10-08 20:06 ` Christopher J. PeBenito
-- strict thread matches above, loose matches on Subject: below --
2009-11-12 21:11 Daniel J Walsh
2009-12-18 15:48 ` Christopher J. PeBenito
2010-02-23 19:44 Daniel J Walsh
2010-08-26 20:47 Daniel J Walsh
2010-09-15 13:20 ` 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=200810070729.16636.russell@coker.com.au \
--to=russell@coker.com.au \
--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.