Registers issue 346 (status: located, severity high). Do not merge without review.
Symptom (review of mesh-catalog #157, 2026-10-09): with picom.conf marked "trusted": false, a settings call setting backend to xrender"; write-pid-path = "<path> adds an option of the caller's; picom then overwrites any file the operator can write (also log-file, shader paths, hiding rules, dummy). #157 was changed to keep the file trusted.
Cause (from the code, controller 4d60628):settingInto pastes plainly(value) raw; only line ends and NUL are refused (settingsHoldOneLine); settings have no type or allowed values; TerminalKeys opens a file's settings to the verb on "trusted": false alone.
Survey of main (7339ce8), every file marked trusted false:dunst dunstrc (INI, one key per line) not open; xdg user-dirs.dirs (shell-sourced format, "${setting:…}") open to command injection for any shell that sources it (none measured on the laptop, where the readers parse it). Recommended: mark user-dirs.dirs trusted again now.
Fix proposed (not built): typed settings (bool, int, enum, string with its file's format), validated at the verb and at composition, quoted at render per format; trusted: false only with every setting typed, checked by module check; until then nothing new goes trusted false.
merge-check.sh passes locally (records, index, cycle, words with the catalogue's list).
Registers issue 346 (status: located, severity high). Do not merge without review.
- **Symptom (review of mesh-catalog #157, 2026-10-09):** with `picom.conf` marked `"trusted": false`, a `settings` call setting `backend` to `xrender"; write-pid-path = "<path>` adds an option of the caller's; picom then overwrites any file the operator can write (also `log-file`, shader paths, hiding rules, `dummy`). #157 was changed to keep the file trusted.
- **Cause (from the code, controller `4d60628`):** `settingInto` pastes `plainly(value)` raw; only line ends and NUL are refused (`settingsHoldOneLine`); settings have no type or allowed values; `TerminalKeys` opens a file's settings to the verb on `"trusted": false` alone.
- **Survey of main (`7339ce8`), every file marked trusted false:** `dunst` dunstrc (INI, one key per line) **not open**; `xdg` user-dirs.dirs (shell-sourced format, `"${setting:…}"`) **open** to command injection for any shell that sources it (none measured on the laptop, where the readers parse it). Recommended: mark user-dirs.dirs trusted again now.
- **Fix proposed (not built):** typed settings (`bool`, `int`, `enum`, `string` with its file's format), validated at the verb and at composition, quoted at render per format; `trusted: false` only with every setting typed, checked by `module check`; until then nothing new goes trusted false.
`merge-check.sh` passes locally (records, index, cycle, words with the catalogue's list).
Found in the review of the picom settings: a backend of xrender"; write-pid-path = "… adds an option of
the caller's. The two files marked trusted false on main are judged (user-dirs.dirs open, dunstrc not),
and typed settings validated at the verb and quoted at render are proposed; until then nothing new goes
trusted false.
Deliverynovox/hq@0ff6bd226726 — delivered since 2026-10-09T10:51:33Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-09 10:40 (new) → proposed (announced): novox/hq#246's head announced
2026-10-09 10:42 proposed → checked (checked): the verdict names this commit
2026-10-09 10:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 10:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 10:51 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@0ff6bd226726` — **delivered** since 2026-10-09T10:51:33Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-09 10:40 (new) → proposed (announced): novox/hq#246's head announced
- 2026-10-09 10:42 proposed → checked (checked): the verdict names this commit
- 2026-10-09 10:42 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 10:51 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 10:51 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Registers issue 346 (status: located, severity high). Do not merge without review.
picom.confmarked"trusted": false, asettingscall settingbackendtoxrender"; write-pid-path = "<path>adds an option of the caller's; picom then overwrites any file the operator can write (alsolog-file, shader paths, hiding rules,dummy). #157 was changed to keep the file trusted.4d60628):settingIntopastesplainly(value)raw; only line ends and NUL are refused (settingsHoldOneLine); settings have no type or allowed values;TerminalKeysopens a file's settings to the verb on"trusted": falsealone.7339ce8), every file marked trusted false:dunstdunstrc (INI, one key per line) not open;xdguser-dirs.dirs (shell-sourced format,"${setting:…}") open to command injection for any shell that sources it (none measured on the laptop, where the readers parse it). Recommended: mark user-dirs.dirs trusted again now.bool,int,enum,stringwith its file's format), validated at the verb and at composition, quoted at render per format;trusted: falseonly with every setting typed, checked bymodule check; until then nothing new goes trusted false.merge-check.shpasses locally (records, index, cycle, words with the catalogue's list).Delivery
novox/hq@0ff6bd226726— delivered since 2026-10-09T10:51:33ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.