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.
Thread beginning with comment 366809
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Security
by boldingd on Wed 3rd Jun 2009 15:56 UTC in reply to "RE: Security"
Member since:

I agree completely. If we, the community of Linux users, want to smugly brag about our platform's excelent security, then it really should support (and support easily!) powerful techniques for limiting the damage that can be done by compromising one of the OS's weakest points, as far as security is concerned. It's a good point that I really don't want someone who compromises my browser to be able to read my files (or, for that matter, to check in on my browser's cached data, or peek at what's going on in other tabs, since I do, for example, my banking on-line).

Reply Parent Score: 0

RE[3]: Security
by Moredhas on Wed 3rd Jun 2009 21:26 in reply to "RE[2]: Security"
Moredhas Member since:

Sorry, I posted that well past my bed time ;) . Trying to sound eloquent, I came off looking like more of an idiot than usual. I wasn't thinking of browser cache or flash cookies and such. I'm surprised sandboxing should be so hard in Linux though...

Reply Parent Score: 2