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
Every unlocker's ID is now the name of its directory in unlockers.d, which is unique in its vault. unlocker select, unlocker remove and the selection unlocker add makes now act on the unlocker named, however close together two were added. This applies to all four types: PGP IDs, which were pgp- and the key's fingerprint, change too. Adding a second PGP unlocker for the same key is still refused. The keychain and Secure Enclave changes were type-checked but not run.
Every unlocker's ID is now the name of its directory in `unlockers.d`, which is unique in its vault. `unlocker select`, `unlocker remove` and the selection `unlocker add` makes now act on the unlocker named, however close together two were added. This applies to all four types: PGP IDs, which were `pgp-` and the key's fingerprint, change too. Adding a second PGP unlocker for the same key is still refused. The keychain and Secure Enclave changes were type-checked but not run.
https://git.eeqj.de/sneak/secret/pulls/109
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 selectandunlocker removethen act on whichever sorts first, the older one, and so does the selectionunlocker addmakes 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
Every unlocker's ID is now the name of its directory in
unlockers.d, which is unique in its vault.unlocker select,unlocker removeand the selectionunlocker addmakes now act on the unlocker named, however close together two were added. This applies to all four types: PGP IDs, which werepgp-and the key's fingerprint, change too. Adding a second PGP unlocker for the same key is still refused. The keychain and Secure Enclave changes were type-checked but not run.#109
Model: opus-5-5