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
670 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%
19fd11b91e
Go to file
Christian Blichmann 19fd11b91e Move GetInternalDataDependencyFilePath() into internal namespace 
Implements #79

PiperOrigin-RevId: 351778836
Change-Id: I726837d8e75880bf5ddfb1a327249dd666adec53
2021-01-14 05:11:22 -08:00
.bazelci Update BazelCI configuration to use Debian 10 2019-10-23 06:10:05 -07:00
.github/workflows Follow-up with more build fixes 2020-12-16 00:09:28 -08:00
cmake Fix dependencies in add_sapi_library 2021-01-06 01:48:55 -08:00
contrib Add directories/README for contributions 2020-07-29 11:32:41 +02:00
oss-internship-2020 Move utility code into sandboxed_api/util 2021-01-13 09:25:52 -08:00
sandboxed_api Move GetInternalDataDependencyFilePath() into internal namespace 2021-01-14 05:11:22 -08:00
.bazelignore Build fixes for recent Bazel versions 2020-09-25 07:25:31 -07:00
.bazelrc Update/simplify linker flags for testcases 2020-12-11 01:12: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 First MVP of a LibTooling based SAPI header generator 2020-05-15 15:35:42 +02:00
.gitmodules Merge pull request #56 from alexelex:master 2020-12-08 03:15:35 -08:00
CMakeLists.txt Add pkg-config files generation. 2020-12-16 06:46:03 -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 Add GitHub workflow build badge 2020-12-16 01:35:32 -08:00
WORKSPACE Update dependencies to latest versions 2020-04-29 06:45:44 -07:00

README.md

Sandbox

Copyright 2019-2020 Google LLC.

Bazel build status CMake 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.