| commit | f6fd27618b446c68520b5e611fab155bb621f83b | [log] [tgz] |
|---|---|---|
| author | Sandboxed API Team <sandboxed-api@google.com> | Wed May 03 08:43:42 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 03 08:45:11 2023 -0700 |
| tree | f1e2b3d4eabb0d08e80d0690762ec1de21e090f1 | |
| parent | 8c53262539b8cb1f658270b385e2ce43eddc68b6 [diff] |
Automated rollback of commit 8c53262539b8cb1f658270b385e2ce43eddc68b6. PiperOrigin-RevId: 529101664 Change-Id: Ica452c6ee8f54b78be09fa830a09d6a89800cf44
Copyright 2019-2022 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.