![]() ![]() I guess my point is that, if you want most/all main-stream distributions to ship and enable SELinux, it needs to be much, much more unobtrusive and self-configuring than it is. Most of the other distributions I’ve used manage to get along fine without it (or, they’re very good at preventing me from noticing it): I wasn’t going to go to much effort to get something working that I wasn’t convinced I really, desperately needed. Basically, I knew (and know now) nothing about what SELinux was and how it worked, and when it became obvious that a non-negligeable amount of work was going to have to go into getting it to work, I decided that it wasn’t worth it and just turned it off. My guess is that any final release for the Mac is still a way off, with the Linux version taking even longer. I personally tested the recent Mac builds of Chromium on my Intel Mac (PPC is not supported because the V8 JavaScript engine isn’t available for PPC), and while it rendered pages just fine, it was still full of bugs and crashed constantly. While Linux’ diversity on all levels is a blessing in that it allows for natural selection and competition, it’s also a curse for developers trying to write an application that can work well on as many distributions as possible. That means no network access, and very limited or no access to files and Mach ports.” After this it gets a bit technical, so to prevent misquoting or errors on my end, I suggest you read the rest of the blog post to get an idea of how it works on Mac OS X.Īgain, we see a case where the fragmentation in Linux as a hindrance to companies releasing software for the platform. In our case we lock down the process pretty tightly. The operating system’s sandboxing APIs are “easy and straightforward”, and makes use of sandbox_init(), “specifying which resources to block for a specific process. On the Mac OS X side of things, the situation looks a lot brighter. The wiki page for Chromium sandboxing on Linux details various mechanisms they’re considering – for now, Chrome on Linux does not do sandboxing. ![]() “Finding a mechanism that is guaranteed to work on end-user’s machines is a challenge,” Moskovich adds. For Linux, Moskovich explains, the situation is a mess because there are several different mechanisms available, and each distribution (of course…) ships with a different mechanism – or none at all. If you browse through the Chromium source code, you’ll find the code relating to Windows sandboxing in the /sandbox directory in the source tree, and it consists of about 100 files. 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. 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. One of the defining features of Google’s Chrome web browse is its sandboxing feature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |