| commit | 3d737e3830867592aa345206b0d69e05009c972e | [log] [tgz] |
|---|---|---|
| author | Sandboxed API Team <sandboxed-api@google.com> | Mon Jan 11 06:58:06 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 11 06:58:30 2021 -0800 |
| tree | 6907240b7fa307decf19e3d7d65826046fcb324f | |
| parent | 7440916b8057620599be721de9b5b4f13029d9bf [diff] |
Automated rollback of commit 7440916b8057620599be721de9b5b4f13029d9bf. PiperOrigin-RevId: 351144593 Change-Id: Ic1401e16dcf2b6b009a9f53395929e31a68cfa77
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.