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 366800
To read all comments associated with this story, please click here.
Member since:

From reading the article it honestly sounds like a bit of a PITA on all operating systems to me.

It takes a load of code on Windows
On Linux, they can't decide which route to go
On OS X, while a framework exists, they are flying blind on knowing which API calls actually work correctly within the framework.

The whole thing sounds like a headache to me on any OS.

Reply Score: 5