mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #419] Splitting --no-sound into --no-speaker and --no-microphone #301
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#301
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 @HulaHoopWhonix on GitHub (Apr 8, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/419
Oz is planning to make pulseaudio restrictions more fine-grained to allow more secure profiles.
Controlling speaker and microphone restrictions separately allows restricting microphone access to a browser (which it has no business accessing) while keeping speaker access for usability.
@netblue30 commented on GitHub (Apr 9, 2016):
Yes, these features are highly desirable. Do they have a description how they do it? How did you find out about it?
@HulaHoopWhonix commented on GitHub (Apr 10, 2016):
Read it here:
https://github.com/subgraph/oz/issues/35
Unfortunately no details are given and nothing implemented yet to look at.
@netblue30 commented on GitHub (Apr 10, 2016):
Thanks, I'll keep an eye on it.
@netblue30 commented on GitHub (Jun 24, 2016):
The bad guy can still go directly to ALSA and bypass PulseAudio. The only way I can see it in this moment is to use private-dev and disable all the sound system.
@HulaHoopWhonix commented on GitHub (Jul 11, 2016):
Orthogonal info:
As part of Flatpak's isolation efforts new low-level permission hooks were added to PulseAudio to allow the microphone vs speaker denial granularity:
Very useful resources linked from the ticket:
https://github.com/flatpak/xdg-desktop-portal/issues/27
I will tell them about the ALSA loophole you talk about.
@netblue30 commented on GitHub (Jul 12, 2016):
Thanks for the information. They still have the problem with ALSA. Quite a number of distributions install ALSA instead of PulseAudio (Lubuntu for example). And there are also users replacing Pulse with ALSA after installing a Linux distro.
I don't see how this will ever get solved without some heavy lifting inside the kernel.
@HulaHoopWhonix commented on GitHub (Jul 16, 2016):
Flatpak devs share more on how they manage to lock down access to pulseaudio while dealing with ALSA.
Please check it out:
https://github.com/flatpak/xdg-desktop-portal/issues/27#issuecomment-233057825
@netblue30 commented on GitHub (Jul 16, 2016):
Let's wait for them to fix PulseAudio.