commit | cb8efdc270fc9b851f46f4b74d7d530ac7195e9f | [log] [tgz] |
---|---|---|
author | Wiktor Garbacz <wiktorg@google.com> | Mon Oct 10 09:38:14 2022 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 10 09:39:01 2022 -0700 |
tree | 1ca07e4be3cb6e2a435671918e9111d8267b36ff | |
parent | b9c2830ebc16d2d3e9e63dfa85bfadc67a6af971 [diff] |
Sandbox2: Graciously handle mapping over Comms/Exec fds Try to move the affected FDs transparently to avoid conflict. PiperOrigin-RevId: 480105375 Change-Id: I0cd093fce120505d1cd4a1d081b3c0e63bf0210a
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.