Block a user
A failed or interrupted backup leaves its half-written blob in the temp directory
Ctrl-C during a backup can end with "FATAL: failed to rollback transaction" and exit 1 instead of the interrupted exit
A reused blob is recorded with the size of a local copy that was never stored, so snapshot verify fails on a good snapshot
A relative file:// path is accepted, so the destination moves with the working directory and a backup can exit 0 and be unrestorable
With the s3.* configuration, a changed bucket or prefix is not detected, and the next backup reports success but cannot be restored
An S3 listing the server marks truncated without a continuation token is taken as complete, so prune can delete blobs still in use
A symlinked metadata/ or blobs/ directory in a file:// destination lists as empty, and prune then deletes every blob
ssh to: the derived key is never offered when the user's ssh config has IdentitiesOnly yes
Defect hunt on next before the release candidate
Part 3: Read restore and verify
Six defects confirmed on next at fa56165, with real runs of ./vaultik (make build, file:// destination, own config and index in a temp dir) and two…
main -> prod: first deploy of pixa
Rework of the body:
- Added: nothing limits how many images are converted at once, and simultaneous requests for one uncached image each fetch and convert it (https://git.eeqj.de/sneak/pixa/issue…
Defect hunt on next before the release candidate
Part 5: Read the storage backends, config and command line
Each item below was confirmed on next at fa56165, with make build's ./vaultik and a throwaway config, index and destination…
Take the keychain and Secure Enclave unlockers out of the build and the release
Remove the keychain and Secure Enclave unlockers (closes #132)
secret vault import cannot succeed on any vault the tool creates, and the mnemonic help points at secret import
One more facet, seen on v1.0.0-rc1 while checking this: on a vault directory that has no pub.age (only reachable by making the directory by hand), secret vault import with `SB_SECRET_MNEMONIC…
A cross-vault
secret mv whose source could not be removed reports "Moved" and exits 0, leaving the secret in both vaults
README does not say that
secret add drops one trailing newline from the value while secret import keeps it
A wrong passphrase is reported as "no identity matched any of the recipients" with advice to make a new unlocker from the mnemonic
A
currentvault file naming a vault that does not exist makes secret list report an empty vault with exit 0