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

SELinux causes 'a lot' of issues for people, and it is highly debatable whether the effort is worth it. Even worse, configuring SELinux is like nothing you will ever do anywhere else on a Linux system.

SELinux very complex and not very well documented, no, I don't want to have to create runtime policies as a response to everything and its configuration and APIs for actually getting it to work are very, very poor. It just isn't worth the effort.


Efforts have been made to document SELinux on Fedora 10 that can be seen on :
http://docs.fedoraproject.org/selinux-user-guide/f10/en-US/index.ht...

There is a SELinux team ready to help as I have found after addressing a bug report. There is a feeling that some "expert" users are reluctant to admit they need help.

Reply Parent Bookmark Score: 2