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
252 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%
fea5e8c485
Go to file
Christian Blichmann fea5e8c485 CMake: Avoid Google Test error when re-configuring with latest Abseil 
Abseil insists on having a Google Test directory, even if we're not going to
run (or even build) the tests.

This changes forces all test settings to `OFF` just for Abseil, allowing
SAPI builds to complete normally. Embedding projects should not be affected,
if they already included Abseil.

PiperOrigin-RevId: 309035680
Change-Id: Ie46297d8b502d92d0c10ef04360e992bcee4964b
2020-04-29 09:17:26 -07:00
.bazelci Update BazelCI configuration to use Debian 10 2019-10-23 06:10:05 -07:00
cmake CMake: Avoid Google Test error when re-configuring with latest Abseil 2020-04-29 09:17:26 -07:00
sandboxed_api Update dependencies to latest versions 2020-04-29 06:45:44 -07:00
.bazelrc Move .bazelrc to correct location next to WORKSPACE 2020-04-28 03:17:28 -07:00
.clang-format Sandboxed API OSS release. 2019-03-18 19:00:48 +01:00
.gitignore Update .gitignore 2020-04-03 02:30:57 -07:00
CMakeLists.txt Update license header with recommended best practices 2020-01-17 05:05:29 -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 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.