Generates sandboxes for C/C++ libraries automatically
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Wiktor Garbacz 7ba0a794d1 Fix check for init process 2 weeks ago
.bazelci BazelCI: Install the packages with `sudo` 1 year ago
.github/workflows GitHub Worklows: Update OS/compiler matrix, deprecate GCC 6 and 7 2 weeks ago
cmake CMake: Make the path to the Clang tool configurable 3 weeks ago
contrib CMake: Update policy settings to 3.26 3 weeks ago
oss-internship-2020 Remove leftover DangerDefaultAllowAll 3 months ago
sandboxed_api Fix check for init process 2 weeks ago
.bazelignore Build fixes for recent Bazel versions 3 years ago
.bazelrc bazel: Set host C++ standard 1 year ago
.clang-format Update `.clang-format` to prefer `&` and `*` to be close to the type 3 years ago
.gitignore Make CMake superbuild behave more similar to `FetchContent` 2 years ago
.gitmodules Remove pffft submodule entry 1 year ago
CMakeLists.txt CMake: Update policy settings to 3.26 3 weeks ago
CONTRIBUTING.md Sandboxed API OSS release. 4 years ago
LICENSE Change license link to HTTPS URL 1 year ago
README.md Update `README.md` with current year 1 year ago
WORKSPACE bazel: Reorganize dependencies 1 year ago

README.md

Sandbox

Copyright 2019-2022 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.