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
550 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%
c99076bf94
Go to file
Christian Blichmann c99076bf94 Replace std::unique_ptr<uint8_t[]> with vector 
No need for the smart pointer indirection when an `std::vector` can also hold
the BPF policy.

PiperOrigin-RevId: 340809220
Change-Id: I8a63567e8042d9ff875cba739e8552db87b6901a
2020-11-05 02:03:46 -08:00
.bazelci Update BazelCI configuration to use Debian 10 2019-10-23 06:10:05 -07:00
cmake Build fixes and parameter passing for the Clang header generator 2020-10-26 01:42:47 -07:00
contrib Add directories/README for contributions 2020-07-29 11:32:41 +02:00
oss-internship-2020 Add an AllowAccess() convenience function to PolicyBuilder 2020-11-03 02:21:21 -08:00
sandboxed_api Replace std::unique_ptr<uint8_t[]> with vector 2020-11-05 02:03:46 -08: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 Merge branch 'master' into gdal_sandbox 2020-10-19 10:05:44 +02:00
CMakeLists.txt Support AArch64 and PPC64 in third party dependencies 2020-10-26 01:22:23 -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.