Skip to content

cblichmann/sandboxed-api

This branch is 3 commits behind google/sandboxed-api:refs/heads/main.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

0ae63ee · Mar 7, 2025
Nov 29, 2024
Nov 29, 2024
Nov 1, 2024
Nov 29, 2024
Feb 6, 2025
Mar 7, 2025
Sep 25, 2020
Nov 4, 2024
Sep 18, 2020
Feb 3, 2021
Feb 10, 2022
Jan 6, 2025
Mar 18, 2019
Jan 28, 2022
Nov 25, 2024
Nov 4, 2024
Jun 9, 2023
Nov 4, 2024
Nov 4, 2024

Repository files navigation

Sandbox

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

About

Generate sandboxes for C/C++ libraries automatically

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C++ 77.8%
  • CMake 10.3%
  • Starlark 6.4%
  • Python 3.1%
  • C 1.7%
  • Shell 0.4%
  • Jsonnet 0.3%