This is normal. chromium-browser uses a setuid sandbox to process
untrusted content. It needs to be setuid to perform some privileged
operations but then drops privileges before processing the input. You
can read more about it here:
http://code.google.com/p/chromium/wiki/LinuxSUIDSandbox
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Changed in: chromium-browser (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016178
Title:
Chromium appears to run as root even without gksudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1016178/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
