Firefox' "Web Content" processes are not confined as strictly as they used to
Previously they would run under their own, stricter AppArmor profile
(torbrowser_plugin_container) but they’re not a different binary
anymore: Firefox now calls its own binary to start a new Web Content
process, so these processes run under the torbrowser_firefox profile.
Parent Task: #15023 (closed)
Related issues
- Related to #12679 (closed)
- Blocks #15334 (closed)
Original created by @intrigeri on 15717 (Redmine)