| commit | c6b8e301e41ae13fcbadbc4878e0d284f3723e4c | [log] [tgz] |
|---|---|---|
| author | Christian Blichmann <cblichmann@google.com> | Wed Sep 25 07:13:33 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 25 07:13:58 2019 -0700 |
| tree | 2bb233049bfb3feaf894c4364247dccc92da689d | |
| parent | ce46cb3fefe3dc8319f00aa37a3283d97901155a [diff] |
This fixes broken _proto_cc_cc_proto build target suffixes. These where inadvertently introduced in an internal cleanup change. This change also removes a C++17-ism in var_proto.h. To make things easier for downstream projects, we should stick to C++11 for the time being. PiperOrigin-RevId: 271117700 Change-Id: I4eaacec88be16e1a561d3f77a61acce0a1af0b9d
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.