Serve node-launcher's hidden prompt, answering sealed to the asker, so a secret typed at the desk is never in the clear (hq ADR 0259 §10)
mesh/merge-gate fail: builds rofi → g14, shanks; no bus step; a manifest the change touches fails the module check: rofi claims node-launcher and says it s…
mesh/repo-check fail: its merge-check.sh failed: files asking for a setting without saying whether it is trusted: 21
mesh/delivery-group group feat/a-secret-given-at-the-desk rejected: a member's own check failed
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
jochen
2026-10-09 11:05:11 +02:00
committed by jschoubben
parent 7339ce8556
commit a33d334008
8 changed files with 231 additions and 2 deletions
+6
View File
@@ -4,6 +4,12 @@ The launcher as a module (novox/hq ADR 0208, research 026/04 and 05).
- Installs `rofi`, claims the mesh's `node-launcher` seat and serves its verb `menu`. Requires
`x11-display` on its own machine.
- **A value nobody sees** (`node-launcher.secret`, novox/hq ADR 0259 §10): a prompt that shows nothing of
what is typed (`rofi -dmenu -password`), whose answer is sealed to the key the asker gives before it
leaves this process — never in the clear on the bus, in the runtime's log or in a call's record. The
controller's `give` asks it to take a module's own secret, such as a bot token, at the desk. It waits at
most 25 seconds. On X11 any program of the operator's account can still read the keys as they are typed
(ADR 0234's accepted residual risk), so the operator types only into a prompt they started.
- **The seat's dmenu-compatible command.** It places `~/.local/bin/dmenu`: choices on standard input,
the chosen one on standard output, exit 1 when nothing was chosen. It runs `rofi -dmenu`, passing
on dmenu's `-p`, `-l` and `-i` and dropping its look options. A script, a notifier or a clipboard