commit | 26f8b0bc611317acc2911a7c405efd2451507584 | [log] [tgz] |
---|---|---|
author | A. Cody Schuffelen <schuffelen@google.com> | Thu Nov 30 21:45:46 2023 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Thu Nov 30 21:45:46 2023 +0000 |
tree | 8beb9375bf52ebf8e075445546e6d330e76f60dc | |
parent | edc5ca5b5562a78f32b2ed4e444b3ac115f2241f [diff] | |
parent | 2a30c5e405df79088a95c6e7b7d590c2dd698db6 [diff] |
Add more files to the sandboxed_api_sandbox2 target am: 549ae36505 am: 88944474d6 am: 2a30c5e405 Original change: https://android-review.googlesource.com/c/platform/external/sandboxed-api/+/2850159 Change-Id: Id420d577188287664bb041a3e212e7a32d495fd4 Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
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.