Ask for the new passphrase in unlocker add when the variable is set (closes #154) #175

Merged
clawbot merged 1 commits from fix/154-new-passphrase-prompt into next 2026-10-15 06:02:32 +02:00
1 Commits
Author SHA1 Message Date
sneak 7a80f4b882 Ask for the new passphrase in unlocker add when the variable is set (closes #154)
check / check (push) Waiting to run
With SB_UNLOCK_PASSPHRASE set, `secret unlocker add passphrase` gave the
new unlocker the passphrase in the variable without asking. It now asks
on the terminal for the new passphrase and uses the variable to unlock
the vault. With no controlling terminal the new unlocker takes the
variable's passphrase, and the output says so.

secret.ErrNoTerminal is exported so that the command can tell a missing
terminal from other failures to read, such as nothing typed or a
mismatched confirmation, which still fail the command.

The in-process tests that add a passphrase unlocker with the variable
set rely on the Docker test phase having no controlling terminal; at a
terminal they would ask.

Model: opus-5-5
2026-10-15 03:33:07 +00:00