All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/2] Allow udev to write in /etc/udev/rules.d
Date: Fri, 20 Dec 2013 15:18:51 -0500	[thread overview]
Message-ID: <52B4A62B.8010209@tresys.com> (raw)
In-Reply-To: <1387210099-30414-2-git-send-email-bigon@debian.org>

On 12/16/13 11:08, Laurent Bigonville wrote:
> From: Laurent Bigonville <bigon@bigon.be>
> 
> Udev is writing persistent rules in /etc/udev/rules.d to ensure the
> network interfaces and storage devices have a persistent name.
> 
> This patch has been taken from the Fedora policy
> ---
>  policy/modules/system/udev.te | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/policy/modules/system/udev.te b/policy/modules/system/udev.te
> index 1643ae0..bcb4bd9 100644
> --- a/policy/modules/system/udev.te
> +++ b/policy/modules/system/udev.te
> @@ -68,7 +68,8 @@ allow udev_t udev_tbl_t:file manage_file_perms;
>  dev_filetrans(udev_t, udev_tbl_t, file)
>  
>  list_dirs_pattern(udev_t, udev_rules_t, udev_rules_t)
> -read_files_pattern(udev_t, udev_rules_t, udev_rules_t)
> +manage_files_pattern(udev_t, udev_rules_t, udev_rules_t)
> +manage_lnk_files_pattern(udev_t, udev_rules_t, udev_rules_t)
>  
>  manage_dirs_pattern(udev_t, udev_var_run_t, udev_var_run_t)
>  manage_files_pattern(udev_t, udev_var_run_t, udev_var_run_t)
 
Merged.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

      reply	other threads:[~2013-12-20 20:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 16:08 [refpolicy] [PATCH 1/2] Label /bin/fusermount like /usr/bin/fusermount Laurent Bigonville
2013-12-16 16:08 ` [refpolicy] [PATCH 2/2] Allow udev to write in /etc/udev/rules.d Laurent Bigonville
2013-12-20 20:18   ` Christopher J. PeBenito [this message]

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=52B4A62B.8010209@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.