Linked by Thom Holwerda on Wed 3rd Jun 2009 11:21 UTC, submitted by Hakime
Google One of the defining features of Google's Chrome web browse is its sandboxing feature. You probably won't realise it's there, but from a security point of view, sand-boxing is one of the most impotant factors in browser security, as it severely limits the amount of damage a security hole can do: sure, you've got a hole in the browser, but thanks to sandboxing, you're pretty much locked in - until you break out of the sandbox, of course. Sandboxing on the Windows variant of Chrome was a "complicated affair", says Chromium developer Jeremy Moskovich, but for the Mac version, it's all a bit easier and more straightforward. On Linux, however, it's a mess.
Permalink for comment 367189
To read all comments associated with this story, please click here.
lsatenstein
Member since:
2006-04-07

I bet this came about because you disabled Selinux and then loaded a bunch of applications. Later you restarted Selinux, but Selinux did not know about them and so, it did what it is supposed to do., Stop you.

You have to set Selinux to rescan the system, in order to catalog or register the objects security properties.

Reply Parent Score: 1