| commit | ee7b76f592c1ca8883dec85aa07b003f1beaa570 | [log] [tgz] |
|---|---|---|
| author | Sandboxed API Team <sandboxed-api@google.com> | Thu Sep 21 06:17:00 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 21 06:17:56 2023 -0700 |
| tree | cd6150fb88e15ceed1b77f0a8c346b08101b5b55 | |
| parent | 4ae281b6a25334da65c441885849c61a12ecd2b3 [diff] |
Automated rollback of commit 4ae281b6a25334da65c441885849c61a12ecd2b3. PiperOrigin-RevId: 567287128 Change-Id: Ia12646e9ad1ebc94f6e26ae1b893b885c0908ca9
Copyright 2019-2023 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.