| commit | d9d45bcfe5acf70af511f630f019e41b84e51808 | [log] [tgz] |
|---|---|---|
| author | Christian Blichmann <cblichmann@google.com> | Thu Nov 21 07:32:42 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 21 07:33:03 2019 -0800 |
| tree | eac7dda6b23eae17ad1df2e68146dc2a6320a909 | |
| parent | 948b75efe90524a7b4795c1d4d39bbb6f800ce71 [diff] |
Fix generator not finding libclang PiperOrigin-RevId: 281745276 Change-Id: I8c55b142a72265f577d6d1e3b673890529428c21
Copyright 2019 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.