Allow network policy to enable transparent TCP capture (#61851)

## What changed

- Add `transparent_tcp` to network configuration and managed requirements, defaulting to off. When enabled, route outbound TCP from managed Linux sandbox commands through the managed SOCKS5 proxy without requiring an executor startup flag.
- Propagate the setting through local and remote execution, require an enabled SOCKS5 proxy, and check the executor's `networkProxyTransparentTcp` capability before remote launches.
- Refresh the live proxy when switching between permission profiles with different network settings.

## Testing

Add coverage for configuration-driven sandbox capture, rejection of unsupported launch contexts, execution parameter propagation, and live permission profile changes.

GitOrigin-RevId: c4db87056de116f433a128806bef673802f35397
This commit is contained in:
viyatb-oai
2026-11-16 18:19:16 +00:00
committed by copyberry
parent fef47a6769
commit effad7568c
29 changed files with 312 additions and 39 deletions
+12
View File
@@ -568,6 +568,18 @@ impl LocalProcess {
params: ExecParams,
telemetry: ProcessTelemetry,
) -> Result<ExecResponse, JSONRPCErrorError> {
// RPC callers must obtain capture from a proxy started by this executor.
// In-process launches can reuse the controller's own managed listener.
if params.requests_transparent_tcp()
&& !params
.network_proxy
.as_ref()
.is_some_and(|launch| launch.proxy.transparent_tcp)
{
return Err(invalid_params(
"transparent TCP requires an executor-local managed proxy".into(),
));
}
self.start_process(params, telemetry)
.await
.map(|(response, _, _)| response)