| commit | 0e8d16e0110b262a376133555d62420e193dbe84 | [log] [tgz] |
|---|---|---|
| author | Anton D. Kachalov <gmouse@google.com> | Mon Dec 14 09:15:40 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Dec 14 09:16:14 2020 -0800 |
| tree | 95eda38752a38089e62b0d955f8d1c92b7787940 | |
| parent | 218435d88eb86d474beda94a0c8551d7f39847b7 [diff] |
Enable shared libraries build and cross-compilation This allows resource-constrained environments to benefit from the space savings of dynamic linking. This is not meant to be used in the general case. PiperOrigin-RevId: 347398828 Change-Id: Ia634959148a31159878f48c44255dd733424a2b8
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.