[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#923747: marked as done (linux-image-amd64: Request to enable CONFIG_USER_NS=y in kernel config)

Your message dated Thu, 07 Mar 2019 22:27:59 +0000
with message-id <bcf4e8db01cf36e344c919ab314d9ed273d41bcd.camel@decadent.org.uk>
and subject line Re: Bug#923747: linux-image-amd64: Request to enable CONFIG_USER_NS=y in kernel config
has caused the Debian Bug report #923747,
regarding linux-image-amd64: Request to enable CONFIG_USER_NS=y in kernel config
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
923747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923747
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Version: 4.19+102
Severity: normal

Dear Maintainer,

   * What led up to the situation?

When I start Brave browser (https://brave.com) in Debian buster/testing,
I get an error that my kernel isn't configured correctly:

    $ brave-browser 
    [8918:8918:0304/181514.182194:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
    Trace/breakpoint trap

This is resolved by adding CONFIG_USER_NS=y to the kernel configuration.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.19.0-2-amd64  4.19.16-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Mon, 2019-03-04 at 18:17 -0500, Nikolas Nyby wrote:
> Package: linux-image-amd64
> Version: 4.19+102
> Severity: normal
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> When I start Brave browser (https://brave.com) in Debian buster/testing,
> I get an error that my kernel isn't configured correctly:
> 
>     $ brave-browser 
>     [8918:8918:0304/181514.182194:FATAL:zygote_host_impl_linux.cc(116)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
>     Trace/breakpoint trap
> 
> This is resolved by adding CONFIG_USER_NS=y to the kernel configuration.

That option is enabled, but the feature is restricted by a sysctl
(kernel.unprivileged_userns_clone) that is off by default.

(The reason for this is discussed at <https://bugs.debian.org/898446>.)

Ben.

-- 
Ben Hutchings
friends: People who know you well, but like you anyway.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: