All of lore.kernel.org
 help / color / mirror / Atom feed
From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [ userdomain patch 1/1] Allow domains that call userdom_tmp_role() to relabel generic user_tmp_t file objects.
Date: Tue, 6 Jul 2010 18:22:44 +0200	[thread overview]
Message-ID: <20100706162243.GB17216@localhost.localdomain> (raw)
In-Reply-To: <4C3354F9.2060404@tresys.com>

On Tue, Jul 06, 2010 at 12:08:25PM -0400, Christopher J. PeBenito wrote:
> On 07/06/10 10:31, Dominick Grift wrote:
> >I encountered this requirement when using poly-instantiation:
> >
> >denied  { relabelfrom } for  pid=14189 comm="sshd" name="system_u:object_r:tmp_t:s0_domg472" dev=dm-3 ino=2884342 scontext=system_u:system_r:sshd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:user_tmp_t:s0 tclass=dir
> >
> >Athough in refpolicy sshd_t does not call userdom_tmp_role (Makes me wonder how refpolicy deals with poly-instantiation.
> 
> Not sure what you mean here, but sshd_t should never be calling
> userdom_tmp_role().  That interface is only for building user
> roles/user domains.

pulseaudio.if: pulseaudio_role:

	userdom_manage_home_role($1, pulseaudio_t)
	userdom_manage_tmp_role($1, pulseaudio_t)
	userdom_manage_tmpfs_role($1, pulseaudio_t)

wm.if: wm_role:

	userdom_manage_home_role($2, $1_wm_t)
	userdom_manage_tmpfs_role($2, $1_wm_t)
	userdom_manage_tmp_role($2, $1_wm_t)

etc

> 
> >Nonetheless, to me it seems to make sense that if one give access to manage a type, you may also want to give relabel perms.
> 
> NAK  Relabeling is special.  There are a few exceptions, but it
> should almost always be separate from manage permissions.
> 
> >Oh, and it is untested (but i commited this to my branch and i will test it when i build a new version)
> >
> >Signed-off-by: Dominick Grift<domg472@gmail.com>
> >---
> >:100644 100644 42d4e8d... 72203a0... M	policy/modules/system/userdomain.if
> >  policy/modules/system/userdomain.if |    6 ++++++
> >  1 files changed, 6 insertions(+), 0 deletions(-)
> >
> >diff --git a/policy/modules/system/userdomain.if b/policy/modules/system/userdomain.if
> >index 42d4e8d..72203a0 100644
> >--- a/policy/modules/system/userdomain.if
> >+++ b/policy/modules/system/userdomain.if
> >@@ -303,6 +303,12 @@ interface(`userdom_manage_tmp_role',`
> >  	manage_sock_files_pattern($2, user_tmp_t, user_tmp_t)
> >  	manage_fifo_files_pattern($2, user_tmp_t, user_tmp_t)
> >  	files_tmp_filetrans($2, user_tmp_t, { dir file lnk_file sock_file fifo_file })
> >+
> >+	relabel_dirs_pattern($2, user_tmp_t, user_tmp_t)
> >+	relabel_files_pattern($2, user_tmp_t, user_tmp_t)
> >+	relabel_lnk_files_pattern($2, user_tmp_t, user_tmp_t)
> >+	relabel_sock_files_pattern($2, user_tmp_t, user_tmp_t)
> >+	relabel_fifo_files_pattern($2, user_tmp_t, user_tmp_t)
> >  ')
> >
> >  #######################################
> >
> >
> >
> >_______________________________________________
> >refpolicy mailing list
> >refpolicy at oss.tresys.com
> >http://oss.tresys.com/mailman/listinfo/refpolicy
> 
> 
> -- 
> 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/20100706/367574ad/attachment.bin 

  reply	other threads:[~2010-07-06 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 14:31 [refpolicy] [ userdomain patch 1/1] Allow domains that call userdom_tmp_role() to relabel generic user_tmp_t file objects Dominick Grift
2010-07-06 16:08 ` Christopher J. PeBenito
2010-07-06 16:22   ` Dominick Grift [this message]
2010-07-06 17:02     ` Christopher J. PeBenito
2010-07-06 17:06       ` Dominick Grift
2010-07-06 17:08         ` Christopher J. PeBenito
2010-07-06 16:31   ` Dominick Grift

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=20100706162243.GB17216@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.