Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I discovered that my version of Chromium (Version 29.0.1547.57 Debian 7.1 (217859)) does not have all the sandbox features turned on by default. Navigating to chrome://sandbox/ gives results:

Sandbox Status
  SUID Sandbox  Yes
  PID name spaces   Yes
  Network namespaces    Yes
  Seccomp-BPF sandbox   No
You are not adequately sandboxed!

Can I turn on the Seccomp-BPF sandbox? My OS stats are:

$ uname -a
Linux compname 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 GNU/Linux

And since I have uninstalled my desktop manager, I normally start Chromium from the commandline like so:

nohup chromium >> /tmp/chromium.nohupout &

However, I have also tried starting Chromium with the --enable-seccomp-sandbox flag, and the sandbox still remains off. When I do this, I get the warning message in stderr:

ATTENTION: default value of option force_s3tc_enable overridden by environment.

Solutions which do not involve me recompiling chromium from source are preferable.

share|improve this question

Sandbox of that type aren't supported on kernel 3.4 or lower; you can use the debian backport to obtain a more recent kernel but keep in mind it'll be less stable.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.