Oliver Kunz 04ed89906b Adding AllowOpen to AllowLlvmSanitizers to avoid having to add AllowOpen in addition when it's only needed for running under the sanitizers.
In cases where SAPI users overwrite the default policy instead of extending it, the sandbox will fail with an `openat` violation. This is automatically inherited in the default policy.

The advantage with this implementation is that we don't expose the open* syscalls when not running under the sanitizers.

PiperOrigin-RevId: 550845188
Change-Id: I151d467848983b00b71ec8447d662394fa7176db
2023-07-25 04:38:43 -07:00
..
2023-07-21 01:53:54 -07:00
2023-05-04 00:46:53 -07:00
2023-07-21 01:53:54 -07:00
2023-07-21 01:53:54 -07:00
2023-03-08 08:09:34 -08:00
2023-03-08 08:09:34 -08:00
2023-07-21 01:53:54 -07:00
2023-03-08 08:09:34 -08:00
2023-03-08 08:09:34 -08:00
2023-03-08 08:09:34 -08:00
2023-01-23 01:42:28 -08:00
2022-01-28 01:39:09 -08:00
2023-05-16 08:51:15 -07:00
2023-03-08 08:09:34 -08:00
2023-03-15 03:29:56 -07:00
2023-03-08 08:09:34 -08:00
2022-01-28 01:39:09 -08:00
2023-03-08 08:09:34 -08:00
2023-02-16 06:07:15 -08:00
2022-12-22 05:00:48 -08:00
2023-03-08 08:09:34 -08:00
2022-01-28 01:39:09 -08:00
2023-03-14 00:04:14 -07:00
2023-03-28 05:50:43 -07:00
2023-03-28 05:50:43 -07:00

Sandbox2

Sandbox2 is a C++ security sandbox for Linux which can be used to run untrusted programs or portions of programs in confined environments. The idea is that the runtime environment is so restricted that security bugs such as buffer overflows in the protected region cause no harm.

Documentation

Detailed developer documentation is available on the Google Developers site for Sandboxed API under Sandbox2.

There is also a Getting Started guide for Sandbox2.