| commit | 221e9290183801bb23ff3def2cf096f0294eaf54 | [log] [tgz] |
|---|---|---|
| author | Christian Blichmann <cblichmann@google.com> | Mon Oct 04 07:17:36 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 04 07:18:36 2021 -0700 |
| tree | 20f1c7d7b102415be69a68813c256d16e6bbb015 | |
| parent | 98e590463b6570feed1e0575e5696543d3016978 [diff] |
Include shell-based tests in OSS builds These were previously dependent on an internal-only testing target. For now, this only works with Bazel, but should enable us to have better test coverage in GitHub actions. Eventually, all of these shell-based tests should be converted to `cc_test`s. PiperOrigin-RevId: 400713615 Change-Id: I1cabb5b72977987ef4a1803480f699b58c4d56e9
Copyright 2019-2021 Google LLC.
The Sandboxed API project (SAPI) makes sandboxing of C/C++ libraries less burdensome: after initial setup of security policies and generation of library interfaces, a 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 its libraries.
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.