commit | 40ff653f0e11c29a21875244f41898bd64607aa6 | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Jun 13 01:14:53 2024 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Thu Jun 13 01:14:53 2024 +0000 |
tree | a4ebe56fe319047144b94bf8290bca25bb6c4bd3 | |
parent | aac71d816e31a520611dbc857015022f70d12b2c [diff] | |
parent | b185838558d73c15b69cd2b6ecc9796df3a3cbeb [diff] |
Snap for 11962796 from b185838558d73c15b69cd2b6ecc9796df3a3cbeb to sdk-release Change-Id: I1f09aa19ed5660bffeef1f2fa7e2742e70bdf7c3
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.