| commit | ec63e07ab9515d95e79c211197c445ef84cefa6a | [log] [tgz] |
|---|---|---|
| author | Xin Li <[email protected]> | Mon Apr 29 22:16:19 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Mon Apr 29 22:16:19 2024 +0000 |
| tree | a4ebe56fe319047144b94bf8290bca25bb6c4bd3 | |
| parent | 0a8fb17472502c9b8a75cb9fef602b4368fa8f9c [diff] | |
| parent | b185838558d73c15b69cd2b6ecc9796df3a3cbeb [diff] |
[automerger skipped] Empty merge of Android 24Q2 Release (ab/11526283) to aosp-main-future am: b185838558 -s ours am skip reason: Merged-In I2a7d93bce8fce583c9916a3b11c366ddfdda3234 with SHA-1 0fc0cacf38 is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/external/sandboxed-api/+/27144054 Change-Id: I531738e1bd4449179964924c668defb78dcd74da 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.