StarMirror
/
sandboxed-api
mirror of https://github.com/google/sandboxed-api
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Generates sandboxes for C/C++ libraries automatically
403 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%
 
 
 
 
 
 
Go to file
Christian Blichmann 88c980218f Build fixes for recent Bazel versions 
We need to add the `oss-internship-2020` and `examples/hello_sapi`
directories to `.bazelignore`, so that `bazel build ...` works on a clean
working copy. This is because the Bazel builds in these directories use their
own `WORKSPACE.bazel` and this does not nest well, leading to all kinds of
hard to debug errors.

PiperOrigin-RevId: 333728800
Change-Id: Ie2e68dd39bf6f8eb21af29d8ae3ae12971b408db
 		2020-09-25 07:25:31 -07:00
.bazelci Update BazelCI configuration to use Debian 10 2019-10-23 06:10:05 -07:00
cmake Restructure the Clang based header generator 2020-09-25 01:14:18 -07:00
contrib Add directories/README for contributions 2020-07-29 11:32:41 +02:00
oss-internship-2020 changed sapi::StatusOr to absl::StatusOr 2020-09-25 12:00:52 +00:00
sandboxed_api Build fixes for recent Bazel versions 2020-09-25 07:25:31 -07:00
.bazelignore Build fixes for recent Bazel versions 2020-09-25 07:25:31 -07:00
.bazelrc Move .bazelrc to correct location next to WORKSPACE 2020-04-28 03:17:28 -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 First MVP of a LibTooling based SAPI header generator 2020-05-15 15:35:42 +02:00
.gitmodules Added GDAL submodule on .gitmodules 2020-09-23 18:46:49 +00:00
CMakeLists.txt Restructure the Clang based header generator 2020-09-25 01:14:18 -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 Update README, graphical assets 2020-03-19 09:27:42 -07:00
WORKSPACE Update dependencies to latest versions 2020-04-29 06:45:44 -07:00

README.md

Sandbox

Copyright 2019-2020 Google LLC.

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.