From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] security_compute_sid: invalid context unconfined_u:system_r:pulseaudio_t
Date: Thu, 20 Sep 2012 09:04:15 -0400 [thread overview]
Message-ID: <505B144F.3020203@tresys.com> (raw)
In-Reply-To: <20120919123003.0764b1e7@eldamar.bigon.be>
On 09/19/12 06:30, Laurent Bigonville wrote:
> Le Tue, 18 Sep 2012 13:07:07 +0200,
> Laurent Bigonville <bigon@debian.org> a ?crit :
>
>> Hi,
>>
>> With the git HEAD of the refpolicy compiled with TYPE = standard and
>> both UBAC = y and UBAC = n, I'm getting the following error:
>>
>> type=SELINUX_ERR msg=audit(1347477364.713:4557): security_compute_sid:
>> invalid context unconfined_u:system_r:pulseaudio_t for
>> scontext=unconfined_u:system_r:pulseaudio_t
>> tcontext=unconfined_u:system_r:pulseaudio_t tclass=unix_stream_socket
>
> OK so this has been fixed by adding the system_r role to the
> unconfined_u user. It seems that Fedora is already doing this, any
> reason it's not in the refpolicy?
>
> Also, pulse audio is now running:
>
> unconfined_u:system_r:pulseaudio_t:s0-s0:c0.c1023 bigon 3820 0.0 0.1 304728 6716 ? S<l 00:13 0:01 /usr/bin/pulseaudio --start --log-target=syslog
>
> Do we also want to have pulseaudio transition to his own context when
> started in the user session?
I'm no expert in pulseaudio, but I suppose it could make sense. The transitions to pulseaudio_t are from initrc_t, mozilla_t, and system_dbusd_t right now.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-09-20 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 11:07 [refpolicy] security_compute_sid: invalid context unconfined_u:system_r:pulseaudio_t Laurent Bigonville
2012-09-19 10:30 ` Laurent Bigonville
2012-09-20 13:04 ` Christopher J. PeBenito [this message]
2012-09-20 13:15 ` Laurent Bigonville
2012-09-21 14:49 ` Daniel J Walsh
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=505B144F.3020203@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.