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
902 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%
0576efe994
Go to file
Christian Blichmann 0576efe994 Update jsonnet README 
PiperOrigin-RevId: 427415134
Change-Id: Ib6a729331bde4e29d89a24298dc9d7ce47c356f3
2022-02-09 02:10:49 -08:00
.bazelci Update BazelCI configuration to use Debian 10 2019-10-23 06:10:05 -07:00
.github/workflows Add GitHub action for Fedora 35 and CMake 2022-01-04 14:55:37 +01:00
cmake CMake: Force inclusion of exported functions in add_sapi_library() 2022-02-07 07:23:34 -08:00
contrib Update jsonnet README 2022-02-09 02:10:49 -08:00
oss-internship-2020 Merge pull request #101 from cblichmann:02jsonnet-contrib 2022-01-28 01:47:32 -08:00
sandboxed_api Tag additional test as not compatible with QEMU user-mode emulation 2022-02-09 01:41:38 -08:00
.bazelignore Build fixes for recent Bazel versions 2020-09-25 07:25:31 -07:00
.bazelrc Remove Bazel workaround for fully_static_link 2022-01-05 01:51:05 -08: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 Jsonnet: Use FetchContent instead of git submodule 2022-01-27 10:34:16 +01:00
CMakeLists.txt CMake: Build contrib sandboxes if requested 2022-02-02 07:02:28 -08: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 README.md with current year 2022-01-31 07:54:57 -08:00
WORKSPACE Change license link to HTTPS URL 2022-01-28 01:39:09 -08:00

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.