mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1110] Brave profile broken #760
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#760
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 @pizzadude on GitHub (Feb 20, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1110
The Brave browser profile is broken
"aptitude show brave" says Brave is version Version: 0.13.4-1
This is the output of launching Brave with firejail:
$ firejail brave
Reading profile /etc/firejail/brave.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/disable-devel.inc
Parent pid 28004, child pid 28005
Child process initialized
[0219/221333.154817:ERROR:resource_bundle.cc(759)] Failed to load /usr/share/brave/chrome_100_percent.pak
Some features may not be available.
[0219/221333.156393:ERROR:resource_bundle.cc(759)] Failed to load /usr/share/brave/chrome_100_percent.pak
Some features may not be available.
[0219/221333.156430:ERROR:resource_bundle.cc(759)] Failed to load /usr/share/brave/chrome_200_percent.pak
Some features may not be available.
Parent is shutting down, bye...
@netblue30 commented on GitHub (Feb 20, 2017):
I loaded the latest 0.13.4-1 deb archive on Debian stable:
It looks like they ported the SUID sandbox from Chromium in their browser. The sandbox is totally broken. In my case it complains about my kernel version. I am using a 4.7 kernel, it has all sandboxing support imaginable.
Pass --no-sandbox as argument to brave, it will disable the sandbox. The browser will come up, but it will complain about not all feature being available. Also, some process crashes - on Ubuntu you'll see a crash report coming.
The only thing we can do in this moment is to wait for them to fix the browser. Once they fix it, we'll have to modify the profile to allow their sandbox to run, similar to what we do for Chromium. I'll mark this as enhancement and keep an eye on Brave. Thanks for bringing this up.
@ibukanov commented on GitHub (Feb 25, 2017):
I could run the brave as is if I whitelist chroot call. I.e. if I replace seccomp in the profile with
then brave starts. But I wonder if I really need to list the default seccomp filter if I just want to remove a call or two from it.
@epsilonPositive commented on GitHub (Mar 12, 2017):
Brave is now counseling users with this problem to enable user namespaces:
https://github.com/brave/browser-laptop/issues/6902
Though this fixes the issue of brave crashing on load, it will still not run in a firejail sandbox.
@netblue30 commented on GitHub (Mar 13, 2017):
@epsilonPositive - try this profile:
@epsilonPositive commented on GitHub (Mar 13, 2017):
This profile does the trick. Along with enabled namespaces, this allows me to run Brave in firejail without using the --no-sandbox option.
Thanks!
@netblue30 commented on GitHub (Mar 16, 2017):
Cool!
@netblue30 commented on GitHub (Apr 3, 2017):
Checked in the profile above.