Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apparmor blocks Tor Browser >= 10.5 starting with MOZ_ENABLE_WAYLAND set #591

Closed
pabs3 opened this issue Jul 7, 2021 · 2 comments · Fixed by #593
Closed

apparmor blocks Tor Browser >= 10.5 starting with MOZ_ENABLE_WAYLAND set #591

pabs3 opened this issue Jul 7, 2021 · 2 comments · Fixed by #593

Comments

@pabs3
Copy link

pabs3 commented Jul 7, 2021

Since Tor Browser 10.5 (release notes, tbb#31729) when the MOZ_ENABLE_WAYLAND environment variable is set, the Firefox build that is part of Tor Browser will try to use Wayland IPC and if that fails then Tor Browser will not start. The current torbrowser.Browser.firefox apparmor profile denies access to the relevant Wayland IPC files/sockets:

Jul 07 08:23:15 audit[437003]: AVC apparmor="DENIED" operation="mknod" profile="torbrowser_firefox" name="/dev/shm/wayland.mozilla.ipc.0" pid=437003 comm="Compositor" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

I was able to workaround this issue using this command:

sudo sh -c 'echo "owner /dev/shm/wayland.mozilla.ipc.[0-9]* rw," > /etc/apparmor.d/local/torbrowser.Browser.firefox ; apparmor_parser -r /etc/apparmor.d/torbrowser.Browser.firefox'
@travankor
Copy link
Contributor

Confirm this works as well. Do you mind sending a PR with the fix as well?

@pabs3
Copy link
Author

pabs3 commented Jul 9, 2021 via email

travankor added a commit to travankor/torbrowser-launcher that referenced this issue Jul 10, 2021
When the environment variable MOZ_ENABLE_WAYLAND is set,
Firefox will try to use Wayland IPC sockets.

Closes torproject#591
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants