registry team mailing list archive

Thread
Date

[Bug 577919] Re: chromium-browser fails to start (guest account, OpenVZ): "Failed to move to new PID namespace: Operation not permitted"

To: registry@xxxxxxxxxxxxxxxxxxx
From: Evan Martin <evan@xxxxxxxxxxxx>
Date: Mon, 08 Nov 2010 21:59:09 -0000
Reply-to: Bug 577919 <577919@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

We have an upstream bug about this here:
  http://code.google.com/p/chromium/issues/detail?id=62248

Note that removing the sandbox makes Chromium on a guest account *less secure* than Chromium in a normal account.
A sandboxed Chromium does all of the page processing (HTML interpretation, running JavaScript) in a process that doesn't have access to the network or disk; by contrast, an apparmor-wrapper Chromium without a sandbox runs all of that at the same privilege as a normal app.

** Bug watch added: code.google.com/p/chromium/issues #62248
   http://code.google.com/p/chromium/issues/detail?id=62248

-- 
chromium-browser fails to start (guest account, OpenVZ): "Failed to move to new PID namespace: Operation not permitted"
https://bugs.launchpad.net/bugs/577919
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for OpenVZ kernel.