Generates sandboxes for C/C++ libraries automatically
Go to file
Wiktor Garbacz 8a7d0d1cb3 Use a nested userns&mntns to pre-pivot_root
This addresses a latency issue - chroot_fs_refs called inside pivot_root
in the kernel can take several milliseconds on machines with many threads
running.
This might not always reduce latency for custom forkservers, as additional
fork can be more costly than pivot_root.

PiperOrigin-RevId: 281306284
Change-Id: If503ac76a70e5438e94caf708d79cb0219c66def
2019-11-19 09:02:28 -08:00
.bazelci Update BazelCI configuration to use Debian 10 2019-10-23 06:10:05 -07:00
cmake Ensure compatibility with CMake 3.10 2019-08-23 05:08:55 -07:00
sandboxed_api Use a nested userns&mntns to pre-pivot_root 2019-11-19 09:02:28 -08:00
.clang-format Sandboxed API OSS release. 2019-03-18 19:00:48 +01:00
.gitignore Add basic .gitignore file 2019-03-26 04:51:40 -07:00
CMakeLists.txt Ensure compatibility with CMake 3.10 2019-08-23 05:08:55 -07: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 Add BazelCI build badge 2019-10-23 07:24:01 -07:00
WORKSPACE Make external usage easier by providing a sapi_deps() workspace rule 2019-06-27 04:27:53 -07:00

Sandboxed API

Copyright 2019 Google LLC.

Sandbox

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.