From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] semaphores
Date: Thu, 14 Apr 2011 11:20:51 -0400 [thread overview]
Message-ID: <4DA710D3.5030205@tresys.com> (raw)
In-Reply-To: <201104150015.11735.russell@coker.com.au>
On 4/14/2011 10:15 AM, Russell Coker wrote:
> type=AVC msg=audit(1302788046.768:5309): avc: denied { unix_read unix_write
> } for pid=6009 comm="mplayer" key=5678293
> scontext=abc:user_r:user_t:s0:c0.c255-s0:c0.c511
> tcontext=abc:user_r:mozilla_t:s0:c0.c255-s0:c0.c511 tclass=sem
>
> In Debian we have a policy based on the 20100524 release. The above is the
> result of trying to run mplayer after doing something in a web browser that
> uses sound (Youtube on Chromium in this case).
>
> Apart from allowing mozilla_t and user_t to access each other's semaphores,
> rewriting the sound libraries, and using ipcrm, how can we solve this?
I don't see any options beyond what you said. I assume mplayer fails
due to this denial? If so, I'm not sure I see what the problem with
allowing it is. Of course I'd rather not, but its not as bad as if the
access were the other way around. User_t already has to interact with
mozilla_t.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2011-04-14 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 14:15 [refpolicy] semaphores Russell Coker
2011-04-14 15:20 ` Christopher J. PeBenito [this message]
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=4DA710D3.5030205@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.