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
1,088 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%
78ee270388
Go to file
Sandboxed API Team 78ee270388 Remove information about in-progress syscalls on process exit. 
PiperOrigin-RevId: 463091104
Change-Id: I402cb61e9e816a20a87274ea874cddf91c101e14
2022-07-25 08:28:25 -07:00
.bazelci BazelCI: Install the packages with sudo 2022-04-01 05:24:17 -07:00
.github/workflows GitHub Actions: Rename workflows, fix libxls 2022-06-15 02:59:23 -07:00
cmake CMake: Move proto import path replacement to build time 2022-06-17 05:56:31 -07:00
contrib libidn2: Use pkg-config for include dir 2022-06-15 00:07:28 -07:00
oss-internship-2020 Update and move lodepng to contrib/ 2022-06-10 04:24:12 -07:00
sandboxed_api Remove information about in-progress syscalls on process exit. 2022-07-25 08:28:25 -07:00
.bazelignore Build fixes for recent Bazel versions 2020-09-25 07:25:31 -07:00
.bazelrc bazel: Set host C++ standard 2022-03-31 05:18:50 -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 Make CMake superbuild behave more similar to FetchContent 2021-02-03 18:15:15 +01:00
.gitmodules Remove pffft submodule entry 2022-02-10 01:41:12 -08:00
CMakeLists.txt cmake: Use configure_file() to implement forced C++ linkage 2022-06-08 23:38:50 -07:00
CONTRIBUTING.md Sandboxed API OSS release. 2019-03-18 19:00:48 +01:00
LICENSE Change license link to HTTPS URL 2022-01-28 01:39:09 -08:00
README.md Update README.md with current year 2022-01-31 07:54:57 -08:00
WORKSPACE bazel: Reorganize dependencies 2022-04-24 23:51:33 -07:00

README.md

Sandbox

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