From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 4/5] Introduce the tmpfiles_t domain
Date: Thu, 14 Aug 2014 15:40:08 -0400 [thread overview]
Message-ID: <53ED1098.1000401@tresys.com> (raw)
In-Reply-To: <1407434738-11937-5-git-send-email-sven.vermeulen@siphos.be>
On 8/7/2014 2:05 PM, Sven Vermeulen wrote:
> +policy_module(tmpfiles, 1.0.0)
[...]
> +type tmpfiles_var_run_t;
> +files_pid_file(tmpfiles_var_run_t)
Nothing really jumped out at me as being a problem, but since most
(all?) distributions have moved towards these files being in /run, I'd
prefer to get away from having "var_run" in the type names. Why don't
we go with something like tmpfiles_run_t or tmpfiles_pid_t?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-08-14 19:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 18:05 [refpolicy] [PATCH 0/5] Supporting tmpfiles Sven Vermeulen
2014-08-07 18:05 ` [refpolicy] [PATCH 1/5] Introduce interface allowing relabeling from/to non-security file types Sven Vermeulen
2014-08-14 19:35 ` Christopher J. PeBenito
2014-08-15 9:31 ` Sven Vermeulen
2014-08-18 14:57 ` Christopher J. PeBenito
2014-08-07 18:05 ` [refpolicy] [PATCH 2/5] Introduce interface to relabel from/to pidfile associated types Sven Vermeulen
2014-08-07 18:05 ` [refpolicy] [PATCH 3/5] Introduce interface to manage all non-security-sensitive resource types Sven Vermeulen
2014-08-07 18:05 ` [refpolicy] [PATCH 4/5] Introduce the tmpfiles_t domain Sven Vermeulen
2014-08-14 19:40 ` Christopher J. PeBenito [this message]
2014-08-14 19:53 ` Dominick Grift
2014-08-15 9:39 ` Sven Vermeulen
2014-08-15 9:35 ` Sven Vermeulen
2014-08-15 15:30 ` Daniel J Walsh
2014-08-18 16:51 ` Christopher J. PeBenito
2014-08-07 18:05 ` [refpolicy] [PATCH 5/5] Give kmod access to tmpfiles 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=53ED1098.1000401@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.