From: dwalsh@redhat.com (Daniel J Walsh)
Date: Fri, 19 Oct 2012 14:11:15 -0400
Subject: [refpolicy] [REVIEW REQUEST] Changes to the pulseaudio policy
 module and its dependencies
In-Reply-To: <20121019180055.GA11667@siphos.be>
References: <1350667422-9219-1-git-send-email-dominick.grift@gmail.com>
	<20121019180055.GA11667@siphos.be>
Message-ID: <508197C3.3010106@redhat.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/19/2012 02:00 PM, Sven Vermeulen wrote:
> On Fri, Oct 19, 2012 at 07:23:42PM +0200, Dominick Grift wrote:
>> The pulseaudio_tmpfs_file_type is assigned to all clients tmpfile file
>> types separately with the pulseaudio_tmpfs_content() interface
>> 
>> pulseaudio_clients atomatically get the access they need to pulseaudio 
>> tmpfs content
>> 
>> read and delete the content
> 
> I have a similar construction with alsa. One thing I am hoping to look
> into soon is a "What if /dev/shm was shm_tmpfs_t instead of tmpfs_t", would
> that make sense?
> 
> It would tighten the scope of such "wide" tmpfs file accesses.
> 
> Wkr, Sven Vermeulen _______________________________________________ 
> refpolicy mailing list refpolicy at oss.tresys.com 
> http://oss.tresys.com/mailman/listinfo/refpolicy
> 
Or just shm_t. Since /tmp is now a tmpfs but we lable it tmpfs_t.

That would allow admins to create a new tmpfs for a specific use and prevent
confined domains from useing it.  Currently we have tmpfs on /run /dev and
/tmp and they all have unigue labels, /dev/shm should problem also.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCBl8IACgkQrlYvE4MpobPafwCfYbj+JgjuGJV1oGAKrRC6JCh/
sSoAmwa1eWx3uitdO3RaG7rQRxuQWrAR
=yUl2
-----END PGP SIGNATURE-----