| commit | fe709502f4ce922d9ee1e1cbebd0a3c41452406b | [log] [tgz] |
|---|---|---|
| author | Wiktor Garbacz <wiktorg@google.com> | Thu Aug 05 07:07:08 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 05 07:07:35 2021 -0700 |
| tree | 550b1a1836666151e20942c605c56fa5a74af994 | |
| parent | e88755256df52514a8309e83de9fc9fc30bc3ca9 [diff] |
Wait for global forkserver when shutting it down Otherwise starting forkserver multiple times will result in zombie processes lingering around. PiperOrigin-RevId: 388926497 Change-Id: Ia9947cce3d9e909edd709b0d3525e1ae8b8bbc51
Copyright 2019-2021 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.