9c21744460
Ideally, we'd seal the embedded SAPI binary using fcntl(). However, in rare cases, adding the file seals `F_SEAL_SEAL | F_SEAL_SHRINK | F_SEAL_GROW | F_SEAL_WRITE` results in `EBUSY` errors. This is likely because of an interaction of `SEAL_WRITE` with pending writes to the mapped memory region (see `memfd_wait_for_pins()` in Linux' `mm/memfd.c`). Since `fsync()` is a no-op on memfds, it doesn't help to ameliorate the problem. On systems where it is enabled, ksmd might also be a source of pending writes. PiperOrigin-RevId: 385741435 Change-Id: I21bd6a9039be4b6298774e837ce3628180ed91a8 |
||
|---|---|---|
| .bazelci | ||
| .github/workflows | ||
| cmake | ||
| contrib | ||
| oss-internship-2020 | ||
| sandboxed_api | ||
| .bazelignore | ||
| .bazelrc | ||
| .clang-format | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| WORKSPACE | ||
Copyright 2019-2021 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.
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.