| commit | a237069702137b065381ae26b161190708547281 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Feb 14 00:16:06 2024 +0000 |
| committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Wed Feb 14 00:16:06 2024 +0000 |
| tree | a4ebe56fe319047144b94bf8290bca25bb6c4bd3 | |
| parent | ae633bab4627a3a7356f2d524233bef909ac740c [diff] | |
| parent | 0a8fb17472502c9b8a75cb9fef602b4368fa8f9c [diff] |
Snap for 11444718 from 0a8fb17472502c9b8a75cb9fef602b4368fa8f9c to 24D1-release Change-Id: I4b1073925929cae55a430cf7e6e77115d86cb4fc
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.