You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Blocked egress is only logged at debug level; add an egress audit log #8
Every policy decision in the proxy is logged with debug!:
IP not in the DNS-pinned set: proxy.rs:219
SNI not in allowlist: proxy.rs:261
No SNI in ClientHello: proxy.rs:268
DNS query refused: dns.rs:73
(Line numbers as of #3 / upstream v0.11.0.) Only the MITM/secret-substitution failure path uses warn! (proxy.rs:284). At the default log level a user running an agent in the sandbox has no idea the agent tried to reach a host that was blocked, or which hosts it successfully reached.
For an agent sandbox, "what did the agent try to talk to" is the main thing an operator wants after a run.
Add an optional --egress-log PATH (and egress_log in shuru.json) that writes one JSON line per decision, so it can be collected without parsing terminal output.
Print a one-line summary at exit: N connections allowed, M blocked, top blocked hosts.
Activity