| commit | 206547591b0bd2dbd6c657841d8817effbb428dc | [log] [tgz] |
|---|---|---|
| author | Oliver Kunz <okunz@google.com> | Mon Mar 14 07:27:57 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 14 07:28:23 2022 -0700 |
| tree | 3685a3844bad75597b3772a9a877fe3463419bb8 | |
| parent | 68eaa815ce240b4e9a999a8eed4cf9fed0f59ad0 [diff] |
Migrate forkserver.proto to proto3 syntax PiperOrigin-RevId: 434458725 Change-Id: I277f76a1a5ebd3eed15c6b3f3e7f849bf6edacea
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.