Generates sandboxes for C/C++ libraries automatically
Go to file
2020-10-02 15:52:29 +00:00
.bazelci
cmake CMake build improvements 2020-09-23 06:43:01 -07:00
contrib
oss-internship-2020 Modified sandbox to limit ioctl. Use .value() instead of manually checking .ok(). 2020-10-02 15:52:29 +00:00
sandboxed_api Use size_t/uintptr_t instead of uintptr_t or uint64_t where appropriate 2020-09-18 07:45:03 -07:00
.bazelrc
.clang-format Update .clang-format to prefer & and * to be close to the type 2020-09-18 02:22:43 -07:00
.gitignore
.gitmodules Added FetchContent command to cmake so that patches are applied automatically to libarchive clone 2020-10-01 19:01:50 +00:00
CMakeLists.txt CMake build improvements 2020-09-23 06:43:01 -07:00
CONTRIBUTING.md
LICENSE
README.md
WORKSPACE

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.