From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH/RFC 2/2] Add minidlna policy
Date: Thu, 2 May 2013 14:26:39 -0400 [thread overview]
Message-ID: <5182AFDF.5090007@tresys.com> (raw)
In-Reply-To: <1367439287.452.23.camel@d30>
On 05/01/13 16:14, Dominick Grift wrote:
> On Wed, 2013-05-01 at 22:09 +0200, Sven Vermeulen wrote:
>> On Wed, May 01, 2013 at 09:12:09PM +0200, Dominick Grift wrote:
>>>> +/etc/minidlna\.conf -- gen_context(system_u:object_r:minidlna_etc_t,s0)
>>>
>>> Can we use type minidlna_conf_t instead for consistency?
>>
>> Ok... but in the contrib/ folder, I find more _etc_t definitions than
>> _conf_t ones:
>>
>> $ grep '^type .*_conf_t' *.te | wc -l
>> 36
>> $ grep '^type .*_etc_t' *.te | wc -l
>> 89
>
> Hmm, i see. I prefer conf in light of self-documenting policy
I prefer it too, but I'd say its not a hard requirement. I think it makes sense, since it ties the name to the concept of a configuration file, rather than a path, which is what _etc_t does. /etc does not consist of only config files.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2013-05-02 18:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 18:36 [refpolicy] [PATCH/RFC 0/2] Introduce minidlna policy Sven Vermeulen
2013-05-01 18:37 ` [refpolicy] [PATCH/RFC 1/2] Add trivnet1 port (8200) Sven Vermeulen
2013-05-01 18:38 ` [refpolicy] [PATCH/RFC 2/2] Add minidlna policy Sven Vermeulen
2013-05-01 19:12 ` Dominick Grift
2013-05-01 20:09 ` Sven Vermeulen
2013-05-01 20:14 ` Dominick Grift
2013-05-02 18:26 ` Christopher J. PeBenito [this message]
2013-05-02 10:59 ` Dominick Grift
2013-05-02 15:41 ` Dominick Grift
2013-05-02 19:23 ` Sven Vermeulen
2013-05-02 19:52 ` Dominick Grift
2013-05-03 7:08 ` Dominick Grift
2013-05-03 12:02 ` Sven Vermeulen
2013-05-03 12:19 ` Dominick Grift
2013-05-03 12:23 ` Dominick Grift
2013-05-03 13:47 ` Christopher J. PeBenito
2013-05-03 17:21 ` Sven Vermeulen
2013-05-03 17:38 ` 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=5182AFDF.5090007@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.