Generates sandboxes for C/C++ libraries automatically
 
 
 
 
 
 
Go to file
Christian Blichmann 41e0ca0a68 CMake: Use min v3.13 and `FetchContent`
This updates the mininum required version of CMake to 3.13, which is
present in Debian Buster.

At the same time, move all of our dependency handling to use
`FetchContent_Declare()`, `FetchContent_Populate()` and
`FetchContent_MakeAvailable()`. Since the latter was ony introduced in
3.14, provide a simple "polyfill" implementation for that.

As an added benefit, the configure step for libffi and libunwind will
now not be re-run every time the `CMakeLists.txt` changes.

Other changes:
- Explicitly spell out that we're testing up to 3.22 in
  `cmake_minimum_version()`
- Rename `check_target()` to `sapi_check_target()` to avoid conflicts
  with Abseil.
2022-01-25 13:59:45 +01:00
.bazelci Update BazelCI configuration to use Debian 10 2019-10-23 06:10:05 -07:00
.github/workflows Add GitHub action for Fedora 35 and CMake 2022-01-04 14:55:37 +01:00
cmake CMake: Use min v3.13 and `FetchContent` 2022-01-25 13:59:45 +01:00
contrib Add directories/README for contributions 2020-07-29 11:32:41 +02:00
oss-internship-2020 Jsonnet: Update with latest Sandboxed API changes 2022-01-24 05:13:03 -08:00
sandboxed_api Simplify `sapi::file::CleanPath` 2022-01-24 05:49:40 -08:00
.bazelignore Build fixes for recent Bazel versions 2020-09-25 07:25:31 -07:00
.bazelrc Remove Bazel workaround for `fully_static_link` 2022-01-05 01:51:05 -08:00
.clang-format Update `.clang-format` to prefer `&` and `*` to be close to the type 2020-09-18 02:22:43 -07:00
.gitignore Make CMake superbuild behave more similar to `FetchContent` 2021-02-03 18:15:15 +01:00
.gitmodules Merge pull request #56 from alexelex:master 2020-12-08 03:15:35 -08:00
CMakeLists.txt CMake: Use min v3.13 and `FetchContent` 2022-01-25 13:59:45 +01:00
CONTRIBUTING.md Sandboxed API OSS release. 2019-03-18 19:00:48 +01:00
LICENSE Sandboxed API OSS release. 2019-03-18 19:00:48 +01:00
README.md Update references to the new documentation 2021-12-14 09:03:29 -08:00
WORKSPACE Update Google Benchmark dependency 2021-12-22 07:11:20 -08:00

README.md

Sandbox

Copyright 2019-2021 Google LLC.

Bazel build status CMake build status

What is Sandboxed API?

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.

Documentation

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.