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 366845
To read all comments associated with this story, please click here.
RE[3]: On the origin of species
by Finalzone on Wed 3rd Jun 2009 19:33 UTC in reply to "RE[2]: On the origin of species"
Finalzone
Member since:
2005-07-06

Every time I have allowed SE Linux to be enabled, within 5 minutes an application I need to run doesn't work with it. And I know, your answer is "don't use that app" or "there is a way to make the app work with SELinux",


What application(s) caused that problem and which distribution is used?

but the reality is I give up after several hours of plunging the depths. It is VERY infuriating, and it really stinks when people say "well, it works for me, must be your problem". That is the Linux way - blame the end user.


It appears it is much easier to give an example without specifying the problem and blame Linux as a whole than simply submitting a bug report to SELinux development and mention what distribution is used.

Reply Parent Bookmark Score: 0