AddAccount: avoid orphaned keyring entry if save_account fails after set_secret #169

Closed
opened 2026-07-27 04:38:39 +00:00 by KofTwentyTwo · 1 comment
KofTwentyTwo commented 2026-07-27 04:38:39 +00:00 (Migrated from github.com)

From the 1.C.1/1.C.2 review (Minor, self-healing): the daemon writes the password to the keyring before persisting the account row; if save_account fails, the keyring keeps a credential with no matching row. Self-healing on retry (deterministic keyring_secret_key + INSERT OR REPLACE). Add a best-effort delete_secret on save failure, or document the orphan.

From the 1.C.1/1.C.2 review (Minor, self-healing): the daemon writes the password to the keyring before persisting the account row; if save_account fails, the keyring keeps a credential with no matching row. Self-healing on retry (deterministic keyring_secret_key + INSERT OR REPLACE). Add a best-effort delete_secret on save failure, or document the orphan.
KofTwentyTwo commented 2026-07-28 14:06:18 +00:00 (Migrated from github.com)

Superseded by #197 (M5) in the roadmap restructuring (milestones M1–M7). The replacement story carries the full, self-contained spec for a remote implementer. See docs/ROADMAP.md, docs/STORY-WORKFLOW.md, docs/HANDOFF.md.

Superseded by #197 (M5) in the roadmap restructuring (milestones M1–M7). The replacement story carries the full, self-contained spec for a remote implementer. See docs/ROADMAP.md, docs/STORY-WORKFLOW.md, docs/HANDOFF.md.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/nuncio#169