| commit | 1f1de9e229905a4f9d2b091b46eb0594509da7fa | [log] [tgz] |
|---|---|---|
| author | Christian Blichmann <cblichmann@google.com> | Tue Jul 14 00:47:14 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jul 14 00:47:54 2020 -0700 |
| tree | 4cf69868fa79ab5c89c5c4b02bdd267f0cdbe8db | |
| parent | 5f35b4fc8ceb7b0e6f8bea102b5971264f947251 [diff] |
Fix logging/display of syscall tables Initializing `absl::Span`s like by assigning them from a temporary array leaves them pointing to invalid data. Due to the way the linker initializes these constant tables, _most_ of them will still be valid _most_ of the time, leading to crashes when running sandboxees with the `--sandbox2_danger_danger_permit_all_and_log` option. PiperOrigin-RevId: 321112099 Change-Id: I891118da08cbb6000b3e2e275618bc4edaa1d020
Copyright 2019-2020 Google LLC.
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.
Detailed 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.