| commit | e88755256df52514a8309e83de9fc9fc30bc3ca9 | [log] [tgz] |
|---|---|---|
| author | Wiktor Garbacz <wiktorg@google.com> | Thu Aug 05 04:15:42 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Aug 05 04:16:11 2021 -0700 |
| tree | 8c93de2b5249983359a4bad9320d63e04ca17e21 | |
| parent | 80ad7bb2b0f82083378b79b71525a49fc5ac64a3 [diff] |
Use `FDCloser` in `Executor` extensively Also really own `exec_fd_` as previously if the executor is destructed without calling `StartSubProcess` the file descriptor would leak. PiperOrigin-RevId: 388901766 Change-Id: I6bbb15ced37a0a832ec5a5228452a3d54ef46ee9
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.