| commit | 0a8fb17472502c9b8a75cb9fef602b4368fa8f9c | [log] [tgz] |
|---|---|---|
| author | A. Cody Schuffelen <[email protected]> | Tue Feb 13 05:34:45 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Feb 13 05:34:45 2024 +0000 |
| tree | a4ebe56fe319047144b94bf8290bca25bb6c4bd3 | |
| parent | 45c743211146d58592c7274622aecf7c6f43df00 [diff] | |
| parent | 0fc0cacf38b3643102b510c6ec0711c6f70c85da [diff] |
Merge remote-tracking branch 'aosp/upstream-main' into 'aosp/main' am: bbaabc5ab3 am: 0fc0cacf38 Original change: https://android-review.googlesource.com/c/platform/external/sandboxed-api/+/2951214 Change-Id: If949d30886219c578c46a15d4f7cab8a3fffffaf Signed-off-by: Automerger Merge Worker <[email protected]>
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.