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
sbx on Windows, layer 2: block the network natively (offline user + firewall) #24
sbx's native Windows backend (layer 1) confines writes with a write-restricted token and per-run ACL grants, and applies job-object limits. All 15 escape tests passed on real Windows in CI (run on main after #16). But it cannot block the network. A policy with network = deny or proxy is refused natively, and auto forwards it to WSL.
Approach (the one OpenAI Codex's Windows sandbox takes)
creates a local sbx-offline user with a random password, stored protected under %ProgramData%\sbx;
adds firewall/WFP rules that block all outbound traffic for that user's SID.
At run time, when the policy needs network deny and setup is present: start the command as that user, still under the write-restricted token, the per-run SID's ACL grants and job limits.
Reporting:enforcement() reports network deny as Enforced when setup is present, otherwise "run sbx setup-windows as administrator". auto prefers native when setup is present. sbx doctor says which.
Proxy: if the firewall/WFP can allow only loopback to the parent's proxy port, the host allowlist works natively too; otherwise it stays on WSL.
CI: the windows-latest job runs sbx setup-windows (the runner is admin) before cargo test -p incord-sandbox. The gated escape tests then prove deny on real Windows.
Activity