question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Brave snap doesn't work without `--no-sandbox` on systems with CONFIG_USER_NS_UNPRIVILEGED disabled

See original GitHub issue
% zgrep CONFIG_USER_NS /proc/config.gz
CONFIG_USER_NS=y
# CONFIG_USER_NS_UNPRIVILEGED is not set
% snap run brave
[2205850:2205850:1014/153436.343633:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox! You probably need to enable user namespaces in your kernel. See https://brave.com/linux for more info.
[1014/153436.343935:ERROR:process_memory_linux.cc(42)] open: Permission denied (13)
/snap/brave/133/opt/brave.com/brave/brave-browser: line 48: 2205850 Trace/breakpoint trap   (core dumped) "$HERE/brave" "$@"
%

This affects users of the linux-hardened kernel on Arch Linux, among others. From https://wiki.archlinux.org/title/Security#Sandboxing_applications:

Warning: Unprivileged user namespace usage (CONFIG_USER_NS_UNPRIVILEGED) is enabled by default in linux (5.1.8 or later), linux-lts (4.19.55-2 or later) and linux-zen (5.1.14.zen1-2 or later) unless the kernel.unprivileged_userns_clone sysctl is set to 0. Since this greatly increases the attack surface for local privilege escalation, it is advised to disable this manually, or use the linux-hardened kernel. For more information see FS#36969.

This does not affect the non-snap version of the browser: image

Related: https://github.com/brave/brave-browser/issues/18723 Slack thread: https://bravesoftware.slack.com/archives/CG7GV6M7Z/p1634147626023000?thread_ts=1634046675.021500&cid=CG7GV6M7Z

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:10 (10 by maintainers)

github_iconTop GitHub Comments

3reactions
wknapikcommented, Oct 22, 2021

The brave-beta-bin and brave-nightly-bin packages are fixed.

0reactions
wknapikcommented, Oct 21, 2021

That looks like a bug in the Arch packaging of these versions.

Left comments for both in AUR, we’ll see if they get responses/fixes.

As for the snap - we can add the suid bit and fix all the issues, but I don’t know how long it’ll take before I can pick it up.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Brave does not run without --no-sandbox
Recently, I installed Kali Linux and I decided to enable the root account because it will be a lot easier for me to...
Read more >
Brave will not start on Arch Linux: No usable sandbox #9955
After installing Brave from source, it won't run. See below for the error message, which says there is no usable chromium sandbox.
Read more >
Brave has sandbox disabled on Arch Linux. Is this a security ...
I installed the brave-beta-bin package from the AUR. When I launched brave, I got a message saying: 'You are using an unsupported ...
Read more >
i switched to brave browser and get no sandbox
Well this will be up to the developers to fix. This from the brave devs: NOTE: If Brave does not start and shows...
Read more >
Fixing the brave sandbox - snap - snapcraft.io
So we have a new brave package, but it seems as though the chromium sandbox is broken. I'm curious, do I have to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found