| commit | 5267d14248eae6bce9cc01ea3eb99a4faa135e8b | [log] [tgz] |
|---|---|---|
| author | Christian Blichmann <cblichmann@google.com> | Mon Jul 12 05:42:57 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 12 05:43:21 2021 -0700 |
| tree | 3c7f94c48e544f520fc7701a6fee06fbb0904d4b | |
| parent | 002cb9ae015c3c27278a4c78cdb89e45d8ebc4ba [diff] |
Take a vector in `Policy::AllowUnsafeKeepCapabilities()` The existing function signature took a `unique_ptr<>` owning a vector, and took `nullptr` to mean an empty set of capabilities. This is more naturally modeled by taking the vector directly and `std::move`-ing it. PiperOrigin-RevId: 384214849 Change-Id: I177f04a06803ae00429b19a1f3f12e7be04d2908
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.