Merge remote-tracking branch 'aosp/upstream-main' into 'aosp/main' am: bbaabc5ab3

Original change: https://android-review.googlesource.com/c/platform/external/sandboxed-api/+/2951214

Change-Id: I2a7d93bce8fce583c9916a3b11c366ddfdda3234
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: a4ebe56fe319047144b94bf8290bca25bb6c4bd3
  1. .bazelci/
  2. .github/
  3. android/
  4. cmake/
  5. contrib/
  6. oss-internship-2020/
  7. sandboxed_api/
  8. .bazelignore
  9. .bazelrc
  10. .clang-format
  11. .gitignore
  12. Android.bp
  13. CMakeLists.txt
  14. CONTRIBUTING.md
  15. LICENSE
  16. METADATA
  17. MODULE_LICENSE_APACHE2
  18. MODULE_LICENSE_BSD
  19. OWNERS
  20. README.md
  21. WORKSPACE
README.md

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.