From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v3 1/3] Support read/append/manage functions for various httpd content
Date: Wed, 27 Jun 2012 10:17:49 -0400 [thread overview]
Message-ID: <4FEB160D.7040508@tresys.com> (raw)
In-Reply-To: <1340745030.12652.15.camel@x220.mydomain.internal>
On 06/26/12 17:10, Dominick Grift wrote:
> On Tue, 2012-06-26 at 22:38 +0200, Sven Vermeulen wrote:
>
>>
>> And while I'm on it, what is the difference between a spec_domtrans and a
>> regular one? Is that only that the transition doesn't occur automatically
>> (i.e. the application has to be SELinux-aware to use it)?
>
> A spec domtrans allows you to specify a target domain.
>
> A normal domtrans takes a single parameter (source) domain.
>
> A spec domtrans takes two parameters (source domain) target domain.
Actually Sven is right on this one. Its supposed to be the difference between an automatic domain transition (via type_transition) and specifying the transition in SELinux-aware code (via setexec). See misc_patterns.spt.
Perhaps we should change "spec" to "setexec" to try to clarify.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-06-27 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 11:07 [refpolicy] [PATCH v3 0/3] Support read/append/manage functions for various httpd content Sven Vermeulen
2012-06-24 11:08 ` [refpolicy] [PATCH v3 1/3] " Sven Vermeulen
2012-06-26 13:22 ` Christopher J. PeBenito
2012-06-26 13:57 ` Dominick Grift
2012-06-26 14:04 ` Christopher J. PeBenito
2012-06-26 20:38 ` Sven Vermeulen
2012-06-26 21:10 ` Dominick Grift
2012-06-27 14:17 ` Christopher J. PeBenito [this message]
2012-06-27 14:31 ` Christopher J. PeBenito
2012-06-24 11:08 ` [refpolicy] [PATCH v3 2/3] Introducing phpfpm_t domain Sven Vermeulen
2012-06-26 13:29 ` Christopher J. PeBenito
2012-06-24 11:09 ` [refpolicy] [PATCH v3 3/3] Allow sysadm_t to administer phpfpm environment 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=4FEB160D.7040508@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.