3a95d9df41
Due to a naming mixup in `oss-internship-2020/curl/CMakeLists.txt`, the necessary `WriteToMemory()` callback was not linked into the sandboxee, leading to a segfault in the sandboxee when trying to run the tests/examples. As another issue, cURL seems to call `sysinfo` and `rt_sigaction` in recent versions and with recent libc. Drive-by changes: - Use the SAPI status macros instead of manually checking `absl::Status` - Put tests in namespace - Some Google C++-style fixes - Start the mock test server only once per test suite Fixes #72 for cURL. Signed-off-by: Christian Blichmann <cblichmann@google.com> |
||
|---|---|---|
| .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-2020 Google LLC.
What is Sandboxed API?
The Sandboxed API project (SAPI) aims to make sandboxing of C/C++ libraries less burdensome: after initial setup of security policies and generation of library interfaces, an almost-identical 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 utilized libraries.
Documentation
Detailed 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.