You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i'll update this when stuff i need gets merged dont mind me for now :)
As far as I understand, access to xdg-run/pipewire-0 carries the same risks as the PulseAudio socket. Anything with access can listen to all audio and any microphones. As such, I think it makes sense to check for it in the audit script, and restrict it in flatpak-permissions-lockdown, just like PulseAudio.
Actually, the more I think about it, perhaps PipeWire socket access should be marked as a fail? Or perhaps we need a new state between warning and fail? Unconditional access to video streams feels rather extreme, considering apps should really be using the camera or screencast portals. It's not quite X11 bad, but it's pretty bad. PulseAudio is obviously flawed too, but less access is probably better. Plus, I'm still researching it, but it seems like we might be able to restrict the ability for certain apps using PulseAudio to make record streams, which I'm not sure is possible with direct PipeWire access...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OUTDATED
i'll update this when stuff i need gets merged dont mind me for now :)
As far as I understand, access to
xdg-run/pipewire-0carries the same risks as the PulseAudio socket. Anything with access can listen to all audio and any microphones. As such, I think it makes sense to check for it in the audit script, and restrict it inflatpak-permissions-lockdown, just like PulseAudio.