Generates sandboxes for C/C++ libraries automatically
 
 
 
 
 
 
Go to file
A. Cody Schuffelen f708270f35 Add `DefaultAction(TraceAllSyscalls)` variant to `PolicyBuilder`
This helps write the kind of 'log, but allow' policy described in
[`notify.h`](b9c84a1f75/sandboxed_api/sandbox2/notify.h (L57)) for all system calls not mentioned explicitly. One use case is writing a "permissive mode" runtime to give more information during development.

PiperOrigin-RevId: 603766051
Change-Id: I3c72f433a1e21c330b5dd9f1ede2faa570b75b09
2024-02-02 13:01:37 -08:00
.bazelci Buildkite: Add specific version for 'clang' Python package 2023-08-08 04:48:59 -07:00
.github/workflows Fix quoting for fedora build action 2023-11-14 07:21:16 -08:00
cmake Do 1 level of recursion on libunwind crashes 2023-09-19 06:50:05 -07:00
contrib Introduce and prefer `AllowMmapWithoutExec` 2023-12-27 02:51:13 -08:00
oss-internship-2020 Introduce and prefer `AllowMmapWithoutExec` 2023-12-27 02:51:13 -08:00
sandboxed_api Add `DefaultAction(TraceAllSyscalls)` variant to `PolicyBuilder` 2024-02-02 13:01:37 -08:00
.bazelignore Build fixes for recent Bazel versions 2020-09-25 07:25:31 -07:00
.bazelrc bazel: Set host C++ standard 2022-03-31 05:18:50 -07: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 Remove pffft submodule entry 2022-02-10 01:41:12 -08:00
CMakeLists.txt CMake: Update policy settings to 3.26 2023-05-11 07:50:52 -07:00
CONTRIBUTING.md Sandboxed API OSS release. 2019-03-18 19:00:48 +01:00
LICENSE Change license link to HTTPS URL 2022-01-28 01:39:09 -08:00
README.md Update Google dependencies 2023-06-09 03:22:00 -07:00
WORKSPACE bazel: Reorganize dependencies 2022-04-24 23:51:33 -07:00

README.md

Sandbox

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