alt Hacker NewsThat's correct. The pattern is: reads allowed, write and network I/O blocked by default.
```
zerobox -- curl https://example.com
Could not resolve host: example.com
```
That's correct. The pattern is: reads allowed, write and network I/O blocked by default.
```
zerobox -- curl https://example.com
Could not resolve host: example.com
```
Oh so it allows ALL file reads?
I'd feel safer with default-deny on reads as well, but I know from past experience that this gets tricky fast - tools like Node.js and uv and Python all have a bunch of files they need to be able to read that you might not predict in advance.
Might still be possible to do that in a DX-friendly way though, if you make it easy to manually approve reads the first time and use that to build a profile that can be reused on subsequent command invocations.