2aff7208fe
## What changed Add `codex tcp-tunnel` and the `codex-tcp-tunnel` crate to forward loopback TCP connections to an explicit target through a TLS-verified HTTP/3 CONNECT proxy. - Require the proxy origin to match an approved HTTPS origin in a supplied policy file. - Read bearer tokens and optional bounded, non-forwarding `x-` headers from stdin. Support token updates for new connections, `LISTENING` and `AUTH_UPDATED` notifications, and shutdown when the control pipe closes in token-update mode. - Preserve the listener across proxy reconnects without replaying TCP streams, and let accepted streams continue while a proxy drains. ## Testing Add tests for hidden CLI parsing, proxy and target validation, credential renewal, control-pipe closure, and invalid input without secret disclosure. A local HTTP/3 proxy test covers token replacement, transport recovery without stream replay, and graceful draining. GitOrigin-RevId: c6af3025301c61e9fe90940cf5a6df0039465e69
1.1 KiB
HTTP/3 TCP tunnel
The ordinary Codex binary includes the hidden codex tcp-tunnel command. It forwards a loopback TCP listener to an explicitly selected host and port through a TLS-verified HTTP/3 CONNECT proxy. The proxy URL must be an exact HTTPS origin in the supplied policy file; the target is provided separately as host:port or [IPv6]:port.
The initial bearer must be provided as a single line on standard input (--auth-token-stdin). With --auth-token-updates-stdin, later lines replace the bearer for new connections, emit AUTH_UPDATED, and closure of the controlling pipe stops the tunnel. With --connect-headers-stdin, the first line is instead a JSON list of ["x-name","value"] pairs; token lines follow. Only non-forwarding x- extension headers are accepted. No header values or credentials belong in the command arguments.
The process emits LISTENING 127.0.0.1:<port> after connecting to the proxy. A proxy handshake does not authorize the target; each local connection makes its own authenticated CONNECT. The listener survives transport reconnects, but TCP streams are never replayed.