All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 07/15] Allow mozilla to read the alsa config files
Date: Mon, 14 Mar 2011 11:29:05 -0400	[thread overview]
Message-ID: <4D7E3441.6040701@tresys.com> (raw)
In-Reply-To: <1299757900.4243.12.camel@tesla.lan>

On 03/10/11 06:51, Guido Trentalancia wrote:
> Hello Dominick !
> 
> On Thu, 10/03/2011 at 09.21 +0100, Dominick Grift wrote:
>> On 03/09/2011 11:46 PM, Guido Trentalancia wrote:
>>> I have the same question as for [PATCH 05/15]. Tested at least with the
>>> moonlight plugin and with the totem plugin. Sounds strange...
>>
>> probably because you were using pulseaudio?
> 
> Indeed. Just do not consider that then.

This makes me think that we need a more abstract pulseaudio interface,
perhaps pulseaudio_client(), which has this access and also others.  It
looks like the interface should include:

pulseaudio_stream_connect()
pulseaudio_exec()
optional_policy(`alsa_read_rw_config()')

and possibly
corenet_tcp_connect_pulseaudio_port()
corenet_sendrecv_pulseaudio_client_packets()

though we probably want to make those conditional.

>>> Regards,
>>>
>>> Guido
>>>
>>> On Wed, 09/03/2011 at 22.13 +0100, Sven Vermeulen wrote:
>>>> In order to allow firefox plugins playing music through ALSA, the mozilla
>>>> domain needs read access on the alsa_rw_config files.
>>>>
>>>> Signed-off-by: Sven Vermeulen <sven.vermeulen@siphos.be>
>>>> ---
>>>>  policy/modules/apps/mozilla.te |    4 ++++
>>>>  1 files changed, 4 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/policy/modules/apps/mozilla.te b/policy/modules/apps/mozilla.te
>>>> index c8c459c..6e0f04f 100644
>>>> --- a/policy/modules/apps/mozilla.te
>>>> +++ b/policy/modules/apps/mozilla.te
>>>> @@ -223,6 +223,10 @@ tunable_policy(`mozilla_read_content',`
>>>>  ')
>>>>  
>>>>  optional_policy(`
>>>> +	alsa_read_rw_config(mozilla_t)
>>>> +')
>>>> +
>>>> +optional_policy(`
>>>>  	apache_read_user_scripts(mozilla_t)
>>>>  	apache_read_user_content(mozilla_t)
>>>>  ')

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

  reply	other threads:[~2011-03-14 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 21:13 [refpolicy] [PATCH 07/15] Allow mozilla to read the alsa config files Sven Vermeulen
2011-03-09 22:46 ` Guido Trentalancia
2011-03-10  8:21   ` Dominick Grift
2011-03-10 11:51     ` Guido Trentalancia
2011-03-14 15:29       ` Christopher J. PeBenito [this message]
2011-03-14 15:36         ` Dominick Grift
2011-03-14 15:39           ` Dominick Grift
2011-03-14 15: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=4D7E3441.6040701@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.