PiperOrigin-RevId: 532473530 Change-Id: Ia5f84073e372a63f70425d0fa68ac178019e80be
|2 weeks ago|
|.bazelci||1 year ago|
|.github/workflows||2 weeks ago|
|cmake||3 weeks ago|
|contrib||3 weeks ago|
|oss-internship-2020||3 months ago|
|sandboxed_api||2 weeks ago|
|.bazelignore||3 years ago|
|.bazelrc||1 year ago|
|.clang-format||3 years ago|
|.gitignore||2 years ago|
|.gitmodules||1 year ago|
|CMakeLists.txt||3 weeks ago|
|CONTRIBUTING.md||4 years ago|
|LICENSE||1 year ago|
|README.md||1 year ago|
|WORKSPACE||1 year ago|
Copyright 2019-2022 Google LLC
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.
Developer documentation is available on the Google Developers site for Sandboxed API.
There is also a Getting Started guide.
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.