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
849 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%
baa1e570b4
Go to file
Christian Blichmann baa1e570b4 CMake build: Skip examples/tests when used via add_subdirectory 
PiperOrigin-RevId: 422512365
Change-Id: I38c6b23d1b33b89346ccf6c6692d50f88c82212b
2022-01-18 03:23:16 -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 build: Skip examples/tests when used via add_subdirectory 2022-01-18 03:23:16 -08:00
contrib Add directories/README for contributions 2020-07-29 11:32:41 +02:00
oss-internship-2020 Update references to the new documentation 2021-12-14 09:03:29 -08:00
sandboxed_api Fix ::sapi:✌️:Char::ToString() 2022-01-17 02:04:50 -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 Merge pull request #56 from alexelex:master 2020-12-08 03:15:35 -08:00
CMakeLists.txt CMake build: Skip examples/tests when used via add_subdirectory 2022-01-18 03:23:16 -08: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 Update references to the new documentation 2021-12-14 09:03:29 -08:00
WORKSPACE Update Google Benchmark dependency 2021-12-22 07:11:20 -08:00

README.md

Sandbox

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