Christian Blichmann a574b66e99 Do not add third_party test targets in CMake build
This way, one can just run `ctest .` in the build directory and it will only
run Sandboxed API and Sandbox2 tests.

PiperOrigin-RevId: 321342543
Change-Id: I42537e64bfb3127dca00bd92a3f7b35ca64004d9
2020-07-15 05:31:50 -07:00
2020-07-14 07:28:16 -07:00
2019-03-18 19:00:48 +01:00
2019-03-18 19:00:48 +01:00
2019-03-18 19:00:48 +01:00
2020-03-19 09:27:42 -07:00

Sandbox

Copyright 2019-2020 Google LLC.

Build status

What is Sandboxed API?

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.

Documentation

Detailed developer documentation is available on the Google Developers site for Sandboxed API.

There is also a Getting Started guide.

Getting Involved

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.

Description
Generates sandboxes for C/C++ libraries automatically
Readme 144 MiB
Languages
C++ 77.8%
CMake 10.8%
Starlark 5.7%
Python 3.3%
C 1.7%
Other 0.7%