Tom Ballinger abd0b3bf2c fix: allow Unix domain socket creation in network-restricted sandbox (#140) ...

When allowedDomains is set, the sandbox enters restricted network mode.
The previous implementation used (allow network* (subpath "/")) to allow
Unix sockets, but socket(AF_UNIX, SOCK_STREAM, 0) is a system-socket
operation that doesn't reference a filesystem path, so (subpath ...) can't
match it. This caused Gradle (FileLockContentionHandler), Docker, and other
tools that create Unix domain sockets to fail with:
  java.net.SocketException: Operation not permitted

The fix uses three explicit Seatbelt rules instead:
1. (allow system-socket (socket-domain AF_UNIX)) - for socket() creation
2. (allow network-bind (local unix-socket ...)) - for bind() operations
3. (allow network-outbound (remote unix-socket ...)) - for connect() operations

This properly separates the socket creation syscall (which has no path
context) from the bind/connect operations (which reference paths).

Fixes: Gradle builds failing in sandbox with allowedDomains configured
Fixes: Docker socket failures in sandbox with allowedDomains configured

2026-02-19 13:24:54 -08:00

..

sandbox

fix: allow Unix domain socket creation in network-restricted sandbox (#140)

2026-02-19 13:24:54 -08:00

utils

feat: add whichSync utility to use Bun.which when available

2026-02-04 07:54:44 +00:00

cli.ts

Re-introduce non-existent deny path protection with mount point cleanup

2026-02-08 19:21:15 -08:00

index.ts

feat: unified checkDependencies API returning SandboxDependencyCheck

2026-01-22 12:22:36 -08:00