Skip to content

Commit c8db905

Browse files
vintaclaude
andcommitted
docs: fold Unreleased changelog into v0.4.0
v0.4.0 was never tagged or published, so the srt 0.0.80 entries are listed under it instead of a separate Unreleased section. Co-Authored-By: Claude <noreply@anthropic.com>
1 parent 50959a4 commit c8db905

1 file changed

Lines changed: 4 additions & 13 deletions

File tree

‎CHANGELOG.md‎

Lines changed: 4 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,5 @@
11
# Changelog
22

3-
## Unreleased
4-
5-
### Breaking Changes
6-
7-
- On Linux, sandboxed commands can't create user namespaces, so Chromium, Electron, Playwright, rootless podman, and nested bubblewrap fail with `unshare failed: Operation not permitted`. Run those tools outside blackwall, since the srt switch that lifts the block also stops `denyWrite` from holding
8-
9-
### Changes
10-
11-
- Upgrades srt to 0.0.80. A refused connection's 403 status line now says why, e.g. `403 host is not on the allow list`, which `curl -sv` shows. Folders named like `[user-id]` no longer keep the sandbox from starting, and on Linux an absent deny path that bubblewrap can't mount no longer blocks every command
12-
- A host blackwall refuses under `"*"` says why in the 403 status line too, e.g. `403 host is on the deny list`, instead of `403 user denied`
13-
- Warns when srt is installed where a sandboxed command can write it, e.g. by a project-local `npm install`, since the command could then replace the sandbox. Install blackwall globally instead. On Linux, srt's warnings about a missing seccomp helper or an outdated bubblewrap show too
14-
153
## v0.4.0 / 2026-10-17
164

175
### Breaking Changes
@@ -29,10 +17,13 @@
2917
- The ad-hoc-signed node copy is `~/.blackwall/node-blackwall`, shown as `node-blackwall` in Little Snitch. Delete `~/.blackwall/blackwall_node`, nothing reads it anymore
3018
- srt settings, `allowPty`, `enableWeakerNetworkIsolation`, and `enableWeakerNestedSandbox`, move to a top-level `srt` object. Each key you set replaces its default, the project's winning over the user's. `overrideDefaults.allowPty` and the others are config errors now, so move them to `srt`
3119
- `blackwall codex` no longer copies `rules` from `~/.codex`, so rules you save in a sandboxed Codex last across launches instead of being replaced by the host's. Put sandbox-specific rules in `~/.codex-blackwall/rules/`
20+
- On Linux, sandboxed commands can't create user namespaces, so Chromium, Electron, Playwright, rootless podman, and nested bubblewrap fail with `unshare failed: Operation not permitted`. Run those tools outside blackwall, since the srt switch that lifts the block also stops `denyWrite` from holding
3221

3322
### Changes
3423

35-
- Upgrades srt to 0.0.79. On 0.0.78, a folder with `[` and `]` in its name, like `[wip] app`, voided every deny inside it, so a sandboxed command could write the project's `.git/hooks`
24+
- Upgrades srt to 0.0.80. On 0.0.78, a folder with `[` and `]` in its name, like `[wip] app`, voided every deny inside it, so a sandboxed command could write the project's `.git/hooks`, and on 0.0.79 a folder named like `[user-id]` kept the sandbox from starting. A refused connection's 403 status line now says why, e.g. `403 host is not on the allow list`, which `curl -sv` shows. On Linux an absent deny path that bubblewrap can't mount no longer blocks every command
25+
- A host blackwall refuses under `"*"` says why in the 403 status line too, e.g. `403 host is on the deny list`, instead of `403 user denied`
26+
- Warns when srt is installed where a sandboxed command can write it, e.g. by a project-local `npm install`, since the command could then replace the sandbox. Install blackwall globally instead. On Linux, srt's warnings about a missing seccomp helper or an outdated bubblewrap show too
3627
- Config values are checked when each config file is read, so a bad range or name pattern is reported with the path of the file it's in. `allowedHosts` entries and `deniedHosts` ranges follow srt's rules; `deniedHosts` names follow blackwall's: `example.com` or `*.example.com` with an optional port, single-label wildcards like `*.localhost` included
3728
- A relative `filesystem.denyRead` or `denyWrite` entry applies to the current folder and every `--add-dir` folder
3829
- Sandboxed commands can't write `.blackwall` in `--add-dir` folders either, not only in the current folder, so they can't write a project config there for you to trust

0 commit comments

Comments
 (0)