| commit | 593b4d550d5569997c65dc1226238da04d4ea61a | [log] [tgz] |
|---|---|---|
| author | Robert Mader <robert.mader@posteo.de> | Mon Sep 06 17:33:17 2021 |
| committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Sep 13 16:29:52 2021 |
| tree | 5ca230613407f65f23e88ca9d583055c83fefd45 | |
| parent | 7f876c8930a1732c898b897739455a95424dc976 [diff] |
Pipewire: Use xdg-portal provided file descriptor The documentation for `OpenPipeWireRemote()` says: > Open a file descriptor to the PipeWire remote where the camera nodes > are available. The file descriptor should be used to create a > pw_core object, by using pw_context_connect_fd. In `InitPipeWire()` we already successfully requested the FD, but then went on and used the unrestricted default socket. This does not matter in non-sandboxed environments, as the stream we want to use is available from both FDs. In flatpak sandboxes, however, this requires to give full Pipewire access to the application. Fix this by simply using the right, restricted FD, and while on it, also make sure to not leak it. This change has already landed in downstream in Firefox, see https://phabricator.services.mozilla.com/D122904 https://phabricator.services.mozilla.com/D124508 Bug: webrtc:13152 Change-Id: I3f8995c54c797e1a90a980f231e496a13cbe65b4 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/230803 Reviewed-by: Joe Downing <joedow@chromium.org> Commit-Queue: Joe Downing <joedow@chromium.org> Cr-Commit-Position: refs/heads/main@{#34983}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.