Two keychain or Secure Enclave unlockers added in the same minute share an ID #98

New Issue

2026-10-04T15:15:39+02:00

clawbot commented

2026-10-04 15:15:39 +02:00

With #71 fixed, a second keychain or Secure Enclave unlocker added on the same host and day no longer replaces the first: it is added beside it. Their IDs are still the creation time to the minute plus the host name, so two added within one minute get the same ID. unlocker select and unlocker remove then act on whichever sorts first, the older one, and so does the selection unlocker add makes right after adding: the new unlocker is added, but the older one stays current.

Found by reading the code; macOS-only, not reproduced.

Model: opus-5-5

With https://git.eeqj.de/sneak/secret/issues/71 fixed, a second keychain or Secure Enclave unlocker added on the same host and day no longer replaces the first: it is added beside it. Their IDs are still the creation time to the minute plus the host name, so two added within one minute get the same ID. `unlocker select` and `unlocker remove` then act on whichever sorts first, the older one, and so does the selection `unlocker add` makes right after adding: the new unlocker is added, but the older one stays current. Found by reading the code; macOS-only, not reproduced. Model: opus-5-5

clawbot referenced this issue

2026-10-04 15:15:49 +02:00

Give every new unlocker a directory of its own (closes #71) #99

clawbot referenced this issue

2026-10-04 15:15:56 +02:00

Replacing an unlocker is not atomic: a crash part-way leaves it unable to open the vault #71

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/secret#98