commit | 59f5fa8042f5cf5782f8b0cbdead139219767109 | [log] [tgz] |
---|---|---|
author | Wiktor Garbacz <wiktorg@google.com> | Mon Aug 16 03:12:39 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 16 03:13:15 2021 -0700 |
tree | 706d783954efee91d194274004162887d70e6d21 | |
parent | 7b31deaed8597d9d3d604f3be0793432bbf13e85 [diff] |
Allow collecting stacktraces on normal process exit This mainly a debugging facility. It makes diagnosing problems where sandboxed process just randomly exits whereas unsandboxed one runs to completion due to differences in the setup/environment much easier. PiperOrigin-RevId: 391005548 Change-Id: Ia19fe6632748da93c1f4291bb55e895f50a4e2b0
Copyright 2019-2021 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.