| commit | c53f2a900f37ab15ccda9f193dcd79215a728dfc | [log] [tgz] |
|---|---|---|
| author | Wiktor Garbacz <wiktorg@google.com> | Fri Aug 28 04:49:15 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Aug 28 04:49:41 2020 -0700 |
| tree | c88d56f8aa3592deda0a05c70e09f4ab8c26eb26 | |
| parent | e7a195ce42a1c3dbcdd1f78c954a4583b85fc789 [diff] |
Automated rollback of commit e7a195ce42a1c3dbcdd1f78c954a4583b85fc789. PiperOrigin-RevId: 328918626 Change-Id: Iabe93ec7062ea6e750e4185e2b0b672a37111ee7
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.