| commit | bc6937ac820ac2b80f86b2738271cb9340b16bda | [log] [tgz] |
|---|---|---|
| author | Sandboxed API Team <sandboxed-api@google.com> | Wed Jan 18 01:44:18 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 18 01:45:01 2023 -0800 |
| tree | cfdf7643980640af97f6ed6453fa19b1e4bffac7 | |
| parent | 58c3f80d5755891bb300bfdf9eda7377d2a98893 [diff] |
Add logging of stack traces of all threads that were terminated by a signal or when the sandboxee did not exit normally. Disabled by default, enabled with a flag. PiperOrigin-RevId: 502807175 Change-Id: Icb5236cbfac0168a2d855c68967f7a1e8bd13fe3
Copyright 2019-2022 Google LLC
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.