All of lore.kernel.org
 help / color / mirror / Atom feed
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [REVIEW REQUEST] Changes to the pulseaudio policy module and its dependencies
Date: Fri, 19 Oct 2012 14:11:15 -0400	[thread overview]
Message-ID: <508197C3.3010106@redhat.com> (raw)
In-Reply-To: <20121019180055.GA11667@siphos.be>

-----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-----

  reply	other threads:[~2012-10-19 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 17:23 [refpolicy] [REVIEW REQUEST] Changes to the pulseaudio policy module and its dependencies Dominick Grift
2012-10-19 17:31 ` Dominick Grift
2012-10-19 18:00 ` Sven Vermeulen
2012-10-19 18:11   ` Daniel J Walsh [this message]
2012-10-19 18:13   ` Dominick Grift
2012-10-19 18:45     ` Sven Vermeulen
2012-10-19 20:51     ` Daniel J Walsh
2012-10-19 21:03       ` Dominick Grift
2012-10-29 12:42 ` 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=508197C3.3010106@redhat.com \
    --to=dwalsh@redhat.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.