All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
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, 06 Jul 2010 13:02:49 -0400	[thread overview]
Message-ID: <4C3361B9.4070606@tresys.com> (raw)
In-Reply-To: <20100706162243.GB17216@localhost.localdomain>

On 07/06/10 12:22, Dominick Grift wrote:
> 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

I'm already working on removing these.

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

  reply	other threads:[~2010-07-06 17:02 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
2010-07-06 17:02     ` Christopher J. PeBenito [this message]
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=4C3361B9.4070606@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.