| commit | 23da55c19a903fca32252e8bda68a4d3d0fa1377 | [log] [tgz] |
|---|---|---|
| author | Sandboxed API Team <sandboxed-api@google.com> | Wed Sep 02 08:46:48 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 03 07:40:33 2020 -0700 |
| tree | b6809b07998cf5d8d97262671758d4e866e0b9cb | |
| parent | 1c833d6f25ae4763eb1e4fb4401f25d2bdc6ef40 [diff] |
Internal BUILD refactoring PiperOrigin-RevId: 329720214 Change-Id: I25fbb94dea17db3bdca6438d17508fa304d9706f
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.