FS#71513 - [torbrowser-launcher] Apparmor profile doesn't work under Wayland

Attached to Project: Community Packages
Opened by arch-dev (arch-dev) - Thursday, 15 July 2021, 08:12 GMT
Last edited by kpcyrd (kpcyrd) - Tuesday, 10 August 2021, 19:58 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To kpcyrd (kpcyrd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Apparmor profile doesn't work under Wayland. The problem is that shared IPC is not whitelisted in
the upstream:

https://github.com/micahflee/torbrowser-launcher/blob/develop/apparmor/torbrowser.Browser.firefox#L116

A simple fix is to add the following line to the profile:

owner /dev/shm/wayland.mozilla.ipc.[0-9]* rwk, # Chromium IPC on Wayland


Additional info:
* package version(s): 0.3.5-1
* config and/or log files etc: no changes to the default apparmor profiles
* link to upstream bug report, if any

Steps to reproduce:

1. install Sway (1:1.6.1-1) and torbrowser-launcher (0.3.5-1)
2. install torbrowser with torbrowser-launcher
3. start apparmor (sudo systemctl start apparmor.service)
4. launch tor-browser (./start-tor-browser.desktop --verbose)
This task depends upon

Closed by  kpcyrd (kpcyrd)
Tuesday, 10 August 2021, 19:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  0.3.5-2
Comment by Jonas Witschel (diabonas) - Thursday, 15 July 2021, 08:43 GMT
Upstream bug report and (not yet merged) pull request:
- https://github.com/micahflee/torbrowser-launcher/issues/591
- https://github.com/micahflee/torbrowser-launcher/pull/593

Loading...