mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #5528] brave: built-in tor connections are blocked #3023
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3023
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ibahnasy on GitHub (Dec 15, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5528
Description
Brave browser can't get connected to it's builtin Tor when firejail is used.
Steps to Reproduce
Run the browser with firejail:
firejail brave-browserThen start a private window with Tor
Expected behavior
Tor should get connected normally.
Actual behavior
Tor fail to connect at all.
Behavior without a profile
Tor works fine
Additional context
Any other detail that may help to understand/debug the problem
Environment
Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)Log
Output of
LC_ALL=C firejail /path/to/programOutput of
LC_ALL=C firejail --debug /path/to/program@ghost commented on GitHub (Dec 15, 2022):
Most likely this is due to
AppArmor. You've got two options here. Both are mentioned in /etc/firejail/brave.profile:If you do use AppArmor (AA) you will need to check your
/etc/apparmor.d/local/firejail-defaultand make sure the relevant rules are enabled. AA caches these rules, so a restart is needed if you make any changes to that file. If you don't use AA then a simple~/.config/firejail/brave.localcontainingignore apparmorshould fix things. Post your files here if you need more help.