| commit | cc4b5f3f2274f0b776e0f2959ccc8627b13383d6 | [log] [tgz] |
|---|---|---|
| author | Mariusz Zaborski <oshogbo@invisiblethingslab.com> | Fri Mar 18 02:00:22 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Mar 18 02:01:39 2022 -0700 |
| tree | 5bd936854d60f342bf103a797f4ada2803311fbc | |
| parent | d0f5f547cb49e5181b0640b80f3332358e90f7d6 [diff] |
Copybara import of the project: -- 8160f26e1a7f986cd5f322fa3a3e9e75b1290a08 by Mariusz Zaborski <oshogbo@invisiblethingslab.com>: zopfli: fix a small typo COPYBARA_INTEGRATE_REVIEW=https://github.com/google/sandboxed-api/pull/137 from oshogbo:doc3 a80d3e728fd69319ce7167387a19b6dc9887c6c8 PiperOrigin-RevId: 435576465 Change-Id: Ia6b4e95e251b425edad4bca31baf9b65ae0809fd
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.