![]() ![]() If it does, great! If it doesn't, you didn't follow the steps on the build page, did you? Hang your head in shame and go actually do it this time. Build this project and make sure everything compiles. Instead they've been nice enough to give you a separate sandbox solution (found in the sandbox folder) that can build standalone. Now, once you get the source, you don't actually have to build chrome in it's entirety (which can take hours!) to use the sandbox. The Google crew knows what they're doing, and aren't keen on useless steps. Alos, it's very important that you follow the instructions on that page VERY CLOSELY. This is big, and will take a while to get, but I've yet to find any reliable shortcuts to checkout that still yeild usable results. Okay, so here's what I found about sandboxing code with Chrome.įirst off, you'll need to go get the chromium source code. Has anyone out there actually sandboxed anything with this yet? Are there any resources that document it's usage or APIs? I would imagine it should be pretty simple, but I'm at a loss for where to start. I just happen to have an application who's design makes it ripe for sandboxing, and was able to get a parent/child process working with it. That's great, and I like the OS-centric design that they have in place (somewhat of a "The OS probably knows how to secure itself better than we do, so we let it" approach.) They also mention in several places that the sandbox itself was designed to not be dependent on Chrome but instead more-or-less standalone so that theoretically any process could be sandboxed as long as the architecture of the program is compatible (sandboxed code must run as it's own process as a child of a non-sandboxed parent.) There are several resources out there that explain how the sandbox in Chrome works and what it does to protect users from malicious code. ![]()
0 Comments
Leave a Reply. |