commit | 13c28403a64751c9d3aa905d5151cf6af53758f6 | [log] [tgz] |
---|---|---|
author | Christian Blichmann <cblichmann@google.com> | Thu Sep 17 03:07:47 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Sep 17 03:08:11 2020 -0700 |
tree | 343f1e07a11a609b2e6ac628ecb5204f27b93246 | |
parent | a68b851c2c353dc00cc87482dc33da6b601984bb [diff] |
Implement system include detection for CMake build The Bazel build already queries the current toolchain for its system include directories. This change brings feature parity and is necessary for systems with unusual include locations. PiperOrigin-RevId: 332195812 Change-Id: Ie81d614d21e90b4bd9edf2084ef80bf0d85dd750
Copyright 2019-2020 Google LLC.
The Sandboxed API project (SAPI) aims to make sandboxing of C/C++ libraries less burdensome: after initial setup of security policies and generation of library interfaces, an almost-identical 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 utilized libraries.
Detailed 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.