| commit | 4289b64aa702a9811045c44935a58c79074884c7 | [log] [tgz] |
|---|---|---|
| author | Wiktor Garbacz <wiktorg@google.com> | Tue Sep 12 06:29:54 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 12 06:30:45 2023 -0700 |
| tree | 7bd2fe6c456fe35473e8e0683c75fb9aca0dd7e4 | |
| parent | 77f62ccb1f52350b3550acb5ba9872ed1ad49f20 [diff] |
Disallow clone3, unsafe clone and unshare flags Ability to create new namespaces and getting capabilities in there exposes a big kernel attack surface. PiperOrigin-RevId: 564703131 Change-Id: I3dcf4c78dca9f51a4b068df16e1b1a69916d727c
Copyright 2019-2023 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.