From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] new runtime udev directory tree (was Re: ANN: Reference Policy Release)
Date: Thu, 28 Jul 2011 11:42:26 -0400 [thread overview]
Message-ID: <4E318362.4000103@tresys.com> (raw)
In-Reply-To: <20110727204704.606662e8q76lz3sw@webmail.tuffmail.net>
On 07/27/11 15:47, Martin Orr wrote:
> On Tue 26 Jul 20:07:29 2011, Guido Trentalancia wrote:
>
>> Thanks very much Christopher for the new release !
>>
>> Just a quick reminder that it seems to me that latest git (and thus
>> implicitly the new release), do not cater proper file contexts
>> definitions yet for new udev directory /run.
>
> Git refpolicy and the new release contain:
> /var/run/udev(/.*)? gen_context(system_u:object_r:udev_tbl_t,s0)
>
> As explained in the relevant commit message, this is intended to label
> /run/udev rather than /var/run/udev.
>
> You need to use some method outside the refpolicy to ensure that
> directories in /run are labelled the same as the corresponding
> directories in /var/run. The easiest is to put
> /run /var/run
> in /etc/selinux/$NAME/contexts/files/file_contexts.subs.
This reminds me, I need to add this file to refpolicy to handle known
substitutions.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-07-28 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 18:44 ANN: Reference Policy Release Christopher J. PeBenito
2011-07-26 18:44 ` [refpolicy] " Christopher J. PeBenito
2011-07-26 19:07 ` [refpolicy] new runtime udev directory tree (was Re: ANN: Reference Policy Release) Guido Trentalancia
2011-07-27 19:47 ` Martin Orr
2011-07-28 15:02 ` Guido Trentalancia
2011-07-28 15:42 ` Christopher J. PeBenito [this message]
2011-08-11 7:03 ` [refpolicy] Status and discussion about rbacsep HarryCiao
2011-08-12 12:42 ` Christopher J. PeBenito
2011-08-12 14:00 ` Christopher J. PeBenito
2011-08-13 8:39 ` HarryCiao
2011-08-16 17:43 ` 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=4E318362.4000103@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.