All of lore.kernel.org
 help / color / mirror / Atom feed
From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [alsa patch 1/1] Interaction with alsa home content by confined users.
Date: Thu, 9 Sep 2010 14:57:53 +0200	[thread overview]
Message-ID: <20100909125752.GD16089@localhost.localdomain> (raw)
In-Reply-To: <4C88D931.2010807@tresys.com>

On Thu, Sep 09, 2010 at 08:55:13AM -0400, Christopher J. PeBenito wrote:
> On 09/08/10 06:41, Dominick Grift wrote:
> >Confined users can manage and relabel alsa home files.
> >
> >Plus some cleanups inspired by example policy.
> >
> >Signed-off-by: Dominick Grift<domg472@gmail.com>
> >---
> [...]
> >diff --git a/policy/modules/roles/staff.te b/policy/modules/roles/staff.te
> >index 0c9876c..f9c23ed 100644
> >--- a/policy/modules/roles/staff.te
> >+++ b/policy/modules/roles/staff.te
> >@@ -53,6 +53,11 @@ optional_policy(`
> >
> >  ifndef(`distro_redhat',`
> >  	optional_policy(`
> >+		alsa_manage_home_files(staff_t)
> >+		alsa_relabel_home_files(staff_t)
> >+	')
> 
> Is there a reason why this needs to be excluded on redhat systems?

Yes confined users can manage and relabel all userdom_user_home_content by default (so its redundant)
> 
> -- 
> Chris PeBenito
> Tresys Technology, LLC
> www.tresys.com | oss.tresys.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20100909/22228b2d/attachment.bin 

  reply	other threads:[~2010-09-09 12:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 10:41 [refpolicy] [alsa patch 1/1] Interaction with alsa home content by confined users Dominick Grift
2010-09-09 12:55 ` Christopher J. PeBenito
2010-09-09 12:57   ` Dominick Grift [this message]
2010-09-09 13:48     ` Daniel J Walsh
2010-09-09 14:59       ` Christopher J. PeBenito
2010-09-09 15:10         ` Dominick Grift
2010-09-09 18:13           ` Daniel J Walsh

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=20100909125752.GD16089@localhost.localdomain \
    --to=domg472@gmail.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.