| commit | dbaf95c724c4eae9cf5a52f346118f8bd69af25a | [log] [tgz] |
|---|---|---|
| author | Christian Blichmann <[email protected]> | Wed Jan 13 09:25:25 2021 -0800 |
| committer | Copybara-Service <[email protected]> | Wed Jan 13 09:25:52 2021 -0800 |
| tree | dc10c285997d747533375be1af6131d8ea31432a | |
| parent | b61b2a37b7adf4ad7c06875a3cdcdf933ef5b749 [diff] |
Move utility code into `sandboxed_api/util` This change should make it less confusing where utility code comes from. Having it in two places made sense when we were debating whether to publish Sandbox2 separately, but not any longer. Follow-up changes will move `sandbox2/util.h` and rename the remaining `sandbox2/util` folder. PiperOrigin-RevId: 351601640 Change-Id: I6256845261f610e590c25e2c59851cc51da2d778
Copyright 2019-2020 Google LLC.
The Sandboxed API project (SAPI) aims to make sandboxing of C/C++ libraries less burdensome: after initial setup of security policies and generation of library interfaces, an almost-identical stub API is generated, transparently forwarding calls using a custom RPC layer to the real library running inside a sandboxed environment.
Additionally, each SAPI library utilizes a tightly defined security policy, in contrast to the typical sandboxed project, where security policies must cover the total syscall/resource footprint of all utilized libraries.
Detailed developer documentation is available on the Google Developers site for Sandboxed API.
There is also a Getting Started guide.
If you want to contribute, please read CONTRIBUTING.md and send us pull requests. You can also report bugs or file feature requests.
If you'd like to talk to the developers or get notified about major product updates, you may want to subscribe to our mailing list or sign up with this link.