mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #462] Is it possible to run a separate instance of pulseaudio inside the sandbox, using xpra to "hear its sounds"? #330
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#330
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DamienGrand on GitHub (Apr 20, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/462
Hello!
It just crossed my mind that, given that Firejail now has X forwarding support and xpra specifically (which has good sound support) it should be possible to block access to host's pulseaudio while running a "local" pulseaudio entirely inside firejail's sandbox, thus achieving flexible sound isolation.
One thing this might be good for is separating microphone and playback access (Xpra has settings for that)
This would for instance allow to isolate Chrome in firejail in a manner that allows sound playback (for watching videos) while at the same time not allowing microphone access.
Possible?
P.S.:
Do I understand correctly that currently, one can't have firejail pass commands to xpra ?(It's not critical for managing sound in the manner described above, but could be useful)
@netblue30 commented on GitHub (Apr 21, 2016):
I'll investigate it, thanks.
@netblue30 commented on GitHub (May 31, 2016):
Unfortunately pulse audio runs as a single instance, so we cannot isolate it.