StarMirror/sandboxed-api
1
0
Fork 0
mirror of https://github.com/google/sandboxed-api.git synced 2024-03-22 13:11:30 +08:00
Code Issues Projects Releases Wiki Activity
Generates sandboxes for C/C++ libraries automatically
1,280 Commits 1 Branch 3 Tags 144 MiB
C++ 77.8%
CMake 10.8%
Starlark 5.7%
Python 3.3%
C 1.7%
Other 0.7%
7a57d32711
Go to file
Wiktor Garbacz 7a57d32711 forkserver: Remove waitpid flag 
It was superseded by sandboxee rusage when using unotify monitor

PiperOrigin-RevId: 557396642
Change-Id: I41f84149227f62d4b7727030f9359834a9b61dbc
2023-08-16 01:33:12 -07:00
.bazelci Buildkite: Add specific version for 'clang' Python package 2023-08-08 04:48:59 -07:00
.github/workflows GitHub Actions: Add workflow to auto-create a pre-release on push 2023-06-08 07:39:48 -07:00
cmake Do not use GIT in FetchContent_Declare 2023-07-19 05:20:28 -07:00
contrib CMake: Update policy settings to 3.26 2023-05-11 07:50:52 -07:00
oss-internship-2020 Remove leftover DangerDefaultAllowAll 2023-03-02 01:22:36 -08:00
sandboxed_api forkserver: Remove waitpid flag 2023-08-16 01:33:12 -07: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.