Evgeny Boger 0fee58a8b9 v0.1.18: run: add --allow-host for host's 127.0.0.1 via host.microsandbox.internal ... New `--allow-host` flag opens DestinationGroup::Host in the egress policy, which is the group addr_classify reserves for the per- sandbox gateway IP (the one resolve_host_dst rewrites to the host's 127.0.0.1 at dial time). End result: a service bound to `127.0.0.1:8080` on the host is reachable from inside the guest as `host.microsandbox.internal:8080` — same name agentd already puts in `/etc/hosts`, no extra setup. Scope: opens the gateway IPs (v4 + v6) only. Not the host's LAN IP, not the guest's own loopback, not metadata. Composes with --allow-egress / --allow-lan / --publish / --auto-publish. Security note in --help mirrors --allow-lan's: anything bound to host loopback (admin UIs, dev DBs, TCP-exposed Docker socket) becomes reachable to a possibly-compromised in-guest process. Vendor bump (microsandbox 2dbfa38) carries the allow_egress_group(Host)-opens-gateway-only test. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-30 15:11:25 +00:00
..
microsandbox@2dbfa3895a	v0.1.18: run: add --allow-host for host's 127.0.0.1 via host.microsandbox.internal	2026-05-30 15:11:25 +00:00