From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/1] Remove pulseaudio filename_trans conflict
Date: Thu, 4 Apr 2013 08:58:36 -0400 [thread overview]
Message-ID: <515D78FC.6060505@tresys.com> (raw)
In-Reply-To: <20130320085326.GA11555@siphos.be>
On 03/20/13 04:53, Sven Vermeulen wrote:
> The pulseaudio_role() interface currently defines explicit filename transitions
> for three files/directories. However, these are already in effect as the domain
> is assigned the pulseaudio_client attribute through the following:
>
> pulseaudio_role()
> -> pulseaudio_run
> -> pulseaudio_domtrans
> -> typeattribute $1 pulseaudio_client
>
> The pulseaudio_client has these file name transitions already (cfr
> pulseaudio.te).
Merged.
> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
> ---
> pulseaudio.if | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/pulseaudio.if b/pulseaudio.if
> index fa3dc8e..45843b5 100644
> --- a/pulseaudio.if
> +++ b/pulseaudio.if
> @@ -31,10 +31,6 @@ interface(`pulseaudio_role',`
> allow $2 pulseaudio_home_t:file { manage_file_perms relabel_file_perms };
> allow $2 pulseaudio_home_t:lnk_file { manage_lnk_file_perms relabel_lnk_file_perms };
>
> - userdom_user_home_dir_filetrans($2, pulseaudio_home_t, dir, ".pulse")
> - userdom_user_home_dir_filetrans($2, pulseaudio_home_t, file, ".esd_auth")
> - userdom_user_home_dir_filetrans($2, pulseaudio_home_t, file, ".pulse-cookie")
> -
> allow $2 { pulseaudio_tmpfs_t pulseaudio_tmpfsfile }:dir { manage_dir_perms relabel_dir_perms };
> allow $2 { pulseaudio_tmpfs_t pulseaudio_tmpfsfile }:file { manage_file_perms relabel_file_perms };
>
>
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2013-04-04 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 8:53 [refpolicy] [PATCH 1/1] Remove pulseaudio filename_trans conflict Sven Vermeulen
2013-04-04 12:58 ` 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=515D78FC.6060505@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.