| commit | a7ad5469a0fe20b841f09c95c1c6bb5c06e4eec2 | [log] [tgz] |
|---|---|---|
| author | Oliver Kunz <okunz@google.com> | Fri Oct 11 05:19:55 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Oct 11 05:20:30 2024 -0700 |
| tree | aa2b65db7b4ae8d2e5ac074ac7f9c3fa357900e3 | |
| parent | 9e07542a03fefa2cf982ba093b099805362df05d [diff] |
Implement ForkServer-based shared network namespace Namespace creation comes at a price. We introduce a means to tie a netns to a forkserver. This means any sandbox started by that forkserver process will have the same netns. PiperOrigin-RevId: 684800270 Change-Id: Ife982bd7bad22ccec9f7fc20b3f127c87622f18d
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.