mirror of
https://github.com/openai/codex.git
synced 2026-11-16 22:00:36 +00:00
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:
@@ -539,6 +539,14 @@ upstream proxy is returned as an error, without retrying directly.
|
||||
|
||||
### Transparent TCP
|
||||
|
||||
In managed `requirements.toml`, set `enabled = true` and `transparent_tcp = true` in the
|
||||
network policy table you already use (`[permissions.network]`, `[network_proxy]`, or
|
||||
`[experimental_network]`). Use one table. Managed SOCKS5 must be enabled.
|
||||
|
||||
Capture defaults to off. When requested through configuration, the controller requires a Linux
|
||||
executor advertising `networkProxyTransparentTcp`. If the sandbox cannot open or configure
|
||||
`/dev/net/tun`, the launch fails before the command runs. To opt in at executor startup:
|
||||
|
||||
```sh
|
||||
codex exec-server --linux-sandbox-transparent-tcp --tcp-upstream-proxy proxy:8088
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user