title: Using the Google Chrome Sandbox
body: <p>There are several resources out there that explain how the sandbox in Chrome works and what it does to protect users from malicious code.</p>
  
  <p><a href="http://blog.chromium.org/2008/10/new-approach-to-browser-security-google.html" rel="noreferrer">Chromium Blog</a><br>
  <a href="http://dev.chromium.org/developers/design-documents/sandbox" rel="noreferrer">Chromium Developer Documentation</a><br>
  <a href="http://dev.chromium.org/developers/design-documents/sandbox/Sandbox-FAQ" rel="noreferrer">Sandbox FAQ</a>  </p>
  
  <p>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.)</p>
  
  <p>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. I've got the Chromium code and... have no idea what to do next. </p>
  
  <p>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.</p>
  
  <p>EDIT: My finding below in the answers!</p>