steerable-egress-proxy
Optional Steerable component: a local, allow-listing CONNECT egress proxy.
Why it exists
The sidecar's OS sandboxes cannot do per-host egress on their own:
macOS Seatbelt degrades hostnames to ports (*:443), and Linux bwrap can
only drop the whole network namespace. The remedy on both is the same —
confine the sidecar to localhost:<proxy port> and let this proxy own the
host list. See docs/spec/safety.md ("Egress allow-list") for the full
threat model.
Usage
steerable-egress-proxy --bind 127.0.0.1:8899 \
--allow api.deepseek.com \
--allow localhost:11434
- Bare
hostentries allow ports 443 and 80, mirroring the Seatbelt profile semantics so the two layers agree. - Fail-closed by construction: an empty allow-list is a startup error,
not "open"; targets off the list get
403; non-CONNECT gets405(unless credential-broker mode is on, below). - Request heads are capped at 16 KiB; upstream dials time out after 10s.
Wire-up with the sandbox: set the sidecar's egress allow-list to
localhost:8899 only, and point the sidecar's HTTP stack at the proxy
(HTTPS_PROXY=http://127.0.0.1:8899 — httpx honors it). The sandbox then
pins the process to the proxy and the proxy enforces the host list.
Credential broker mode (W2.2.2)
STEERABLE_EGRESS_SECRET='Bearer sk-...' \
steerable-egress-proxy --bind 127.0.0.1:8899 \
--allow api.deepseek.com \
--inject-host api.deepseek.com \
--inject-secret-env STEERABLE_EGRESS_SECRET
With an inject rule, plain-HTTP requests naming that host in the absolute
URI are forwarded to the host over TLS with the credential header
injected. The sandboxed sidecar then uses http://api.deepseek.com as its
provider baseUrl (note: http) with the proxy as HTTP_PROXY, and
never holds the real token — the secret exists only in the proxy process
(env var, never argv).
Rules: off-host plain-HTTP → 403; no rule → non-CONNECT stays 405;
client-supplied credential headers are stripped, never forwarded; chunked
request bodies → 501. One inject rule per proxy. --inject-header
switches the header (e.g. x-api-key); --inject-scheme http exists for
loopback test upstreams only. TLS is never intercepted — the CONNECT path
stays opaque byte plumbing.
1 maintainer
Release files for steerable-egress-proxy 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| steerable_egress_proxy-0.6.1.tar.gz | 16.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| steerable_egress_proxy-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.1 kB
Release files / steerable_egress_proxy-0.6.1.tar.gz
| Download URL | steerable_egress_proxy-0.6.1.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
83b7d8d81c7476a4ba38f9d373fbec8ac3477cb5e056c8bc2f889a7cf1259090
|
|
BLAKE2b-256 checksum How to use checksums |
78dd09da9f793dca14d2c8b3db531d407f3b0e5d8b701f0dd134925314934eda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / steerable_egress_proxy-0.6.1-py3-none-any.whl
| Download URL | steerable_egress_proxy-0.6.1-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bead932633ec9592944c9b54b0adb98e4a229a9767325e2b2f5607d5673ca764
|
|
BLAKE2b-256 checksum How to use checksums |
002e6b83885217988a8e33fb23ac91478bc2829581692aa1cb9a46e9b53c73d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
