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

Merged
clawbot merged 1 commits from issue-71-unlocker-own-directory into next 2026-10-04 16:58:46 +02:00
1 Commits
Author SHA1 Message Date
sneak be56ae533c Give every new unlocker a directory of its own (closes #71)
check / check (push) Waiting to run
A passphrase unlocker added to a vault that had one, and a PGP, keychain
or Secure Enclave unlocker added on the same day as another of its type,
were written into the existing unlocker's directory file by file, so a
crash part-way left a current unlocker whose files did not belong
together.

Unlocker directories, keychain items and Secure Enclave keys are now
named with the time to the nanosecond, and secret.WriteDir refuses a
directory that exists. Adding a passphrase unlocker writes the new one,
points current-unlocker at it, and only then removes the vault's other
passphrase unlockers.

Model: opus-5-5
2026-10-04 14:28:25 +00:00