From: Russell Coker <russell@coker.com.au>
To: selinux-refpolicy@vger.kernel.org
Subject: pipewire etc
Date: Sat, 27 Jun 2026 10:02:09 +1000 [thread overview]
Message-ID: <2540904.xDKz687JKs@xev> (raw)
Why do we need different policies for alsa, pipewire, and pulseaudio? They
all do the same things, why not just have an audioserver policy that supports
all of them?
Why do we need an ifdef for server vs user operation of pipewire? Why not
just have a policy with a pipewire_t for the system daemon and pipewire_user_t
for the user process?
https://wiki.archlinux.org/title/
PipeWire#Sharing_audio_devices_with_computers_on_the_network
For people wondering as I did why we even need a pipewire_user_t domain, the
above section of the Arch Wiki documents sharing audio via Airplay and RTP
among others - definitely need that isolated!
Is a pipewire_client_t domain just for the test program really useful?
It looks like the policy is well structured and replacing the cruft from years
of support of alsa and pulseaudio is a good thing. So I think we should go
all the way and delete the separate policy for the old sound servers.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next reply other threads:[~2026-06-27 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-27 0:02 Russell Coker [this message]
2026-06-27 6:19 ` pipewire etc 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=2540904.xDKz687JKs@xev \
--to=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/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.