| commit | 920fd85c6918cb6a3d25850c1f40e0a50008678e | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Sat Dec 02 02:15:19 2023 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Sat Dec 02 02:15:19 2023 +0000 |
| tree | 8beb9375bf52ebf8e075445546e6d330e76f60dc | |
| parent | 3dcb11301954daadbb0bcdfa2595758553198ad1 [diff] | |
| parent | 26f8b0bc611317acc2911a7c405efd2451507584 [diff] |
Snap for 11169761 from 26f8b0bc611317acc2911a7c405efd2451507584 to 24Q1-release Change-Id: I3bee264e556b8d5c72415851d1cd2288a10f16e5
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.