docs: docker host-root mount deny in CHANGELOG and SETTINGS
This commit is contained in:
1 parent
0f73d7ee01
commit
a308a022b7
2 files changed
+2
-1
No files matched your search
@@ -23,6 +23,7 @@ The BDR-125 context queue is delivered: phases 0, 0b, 4a, 1, 5, 2 and 4b-4d ship
|
||||
- `MEM_LEGACY_RE`, the environment override of `memory_legacy_status`'s v1 line selector announced in 3.0.0, and that function's `<end>` argument: the signature is now `memory_legacy_status <file> <ID> [<re>]` (third argument = line selector, the range end follows the ID's prefix). The decision selector `_MEM_LEGACY_BDR_RE` lives in `lib/memory.sh`; `RECONCILE_BDR_RE` is gone from `lib/reconcile.sh`. Test: `lib/tests/memory.test.sh` T15-env-selector-ignored.
|
||||
|
||||
### Fixed
|
||||
- `settings.json` denies a docker mount of the host root in 7 spellings: `/:/` after a space (`-v`, `--volume`) or after `=` (`-v=`, `--volume=`), the attached `-v/:/`, and `--mount` with `source=/` or `src=/` followed by a comma or a space. Each shape is denied under any subcommand and four prefixes (`docker`, `rtk docker`, `*/rtk docker`, `*/docker`): 28 rows. The 3.0.0 row `Bash(docker run * -v /:/*)` needed a token before `-v`, so a plain `docker run -v /:/x img` passed, and `Bash(docker run -v /:*)` (legacy prefix syntax) matched nothing. Both stay until the next removal window. The `autoMode.soft_deny` docker entry now names `docker create`, `docker container run` and `docker compose up` next to `docker run`. Left to the classifier: attached flag clusters (`-itv/:/x`), a host path from a variable or a substitution, root aliases (`//`, `/.`, `/..`), upper-case mount keys and compose-file volumes. Test: `lib/tests/push-guard.test.sh` T41 locks the 28 rows.
|
||||
- `cc <name> [profile]` (lib/cc.sh) raises the session's `oom_score_adj` to 500 before `exec claude` (raise-only, silent if the write fails). sshd's systemd override `OOMScoreAdjust=-1000` was inherited through tmux and dtach by every claude started with `cc`, so the OOM killer never picked a runaway session; `systemd-run --scope` rejects that property, hence the write inside the session (BLK-044). Test: `lib/tests/cc.test.sh` T7-oom.
|
||||
- `lib/project-rules.sh` (`extract`, `emit`): the out-path check resolves the rule file's first existing parent physically and refuses (rc 2, `must stay under the project`) a path a symlinked component sends outside the project; 3.0.0 checked `..` lexically only. `emit` goes through the same check and reports `cannot create` or `not written` (no partial file) with rc 2 where it printed `emitted`. An `extract` that wrote the rule but fails to rewrite CLAUDE.md keeps the rule file and the rewritten text in a temp file and names both on stderr with the command to complete or abort; it used to delete both. `/onboard` and `/init-project` keep an existing rule on an rc 2 ending in ` exists` and stop on any other rc 2. Tests: `lib/tests/project-rules.test.sh` T9h (re-asserted), T9z3 to T9z13.
|
||||
- `lib/memory.sh`: `memory_legacy_status` (the v1 status reader behind `memory.sh upgrade`, `/reconcile`, `/prune-memory`) ends an entry's range at the next heading of another entry of the same prefix, any level, outside a code fence, or at `## Index`: a `### BLK-` entry no longer lends its status to the `## BLK-` entry above, and a trailing `## Index` is no longer read. `memory.sh upgrade` on an entry with no strict status word writes the single word of its v1 `Status`/`Statut` label as the dated upgrade status line; when the `## Index` cell disagrees the body word wins and stderr says `kept body <word>, dropped Index <cell>` (the Index used to win); an Index `superseded`/`deprecated` still wins; a label without exactly one word is refused on a blocker and leaves the Index cell on a decision. Control characters from a v1 line or an Index cell print as `?`. `memory.sh journal` leaves exactly one blank line before a new date heading (a file ending with a blank line got two, one without a final newline got none). Tests: `lib/tests/memory.test.sh` T14l-gap, T15-statut-*, T15-bdr-*, T15-idx-*, T15-ctl-*, T15-trailing-index-not-read.
|
||||
|
||||
@@ -141,7 +141,7 @@ local trace, and the brief had authorized it. What holds now, by tier:
|
||||
|---|---|---|
|
||||
| Transfer and mirror tools (`lftp`, `sftp`, `ftp`, `curl -T`), `rsync --delete`, `xargs rm`, pipe-to-shell | `permissions.deny` | Never needed in a session: Claude explains a deploy, the user runs it. Static, so it resolves before the classifier and inside sub-agents. |
|
||||
| `chmod`/`chown -R`, `sudo`/`doas`/`pkexec`, disk tools (`dd`, `mkfs`, `shred`…), `chattr` | `permissions.deny` | The user runs them by hand. |
|
||||
| Docker volume drops, `system prune`, `compose down -v`, `--privileged`, the docker socket, `-v /:` | `permissions.deny` | Promoted from `soft_deny`: no in-session clearance for data drops. |
|
||||
| Docker volume drops, `system prune`, `compose down -v`, `--privileged`, the docker socket, a host-root mount (`-v /:`, `--volume /:`, `--mount source=/` or `src=/`, any subcommand, typed, through `rtk` or by absolute path) | `permissions.deny` | Promoted from `soft_deny`: no in-session clearance for data drops. |
|
||||
| Git history destruction (`push --delete`/`--mirror`/`:ref`/`--force-with-lease`, `branch -D`, `filter-branch`, `reflog expire`, `stash clear`/`drop`, `clean -f`), `--no-verify`, `core.hooksPath` | `permissions.deny` | A remote is the backup; nothing rewrites or deletes what it holds. |
|
||||
| Writing the human-only `gitflow.*` toggles: any `git … config` spelling, section remove/rename, `git -c`, the git config env overrides, Edit/Write of git config files | `permissions.deny` | Claude never flips the mode that binds it. Side effect: the trailing glob also matches the bare read, so Claude cannot read `gitflow.autopush` through `git config`; hooks and `lib/gitflow.sh` still do, and skills read it through `gitflow.sh push-mode`. |
|
||||
| Merging: `git merge`, `bash`/`sh` `…gitflow.sh finish` | `permissions.ask` | `finish` runs only on an explicit human signal: one prompt per merge, and a declined prompt merges nothing. `git -C <dir> merge` and a sourced `gitflow_finish` escape the static rules; the sourced form falls to `autoMode.soft_deny` "Static rule blind spots". |
|
||||
|
||||
Reference in new issue
Block a user