Block a user
A gpg failure is reported as only its exit status; gpg's reason on stderr is dropped
A secret larger than about half the locked-memory limit crashes
secret add, import and generate secret with a panic
The passphrase prompt reads stdin, so
secret add --force with a piped value and secret encrypt/decrypt from stdin cannot ask for the passphrase
secret decrypt and secret encrypt truncate the --output file before they can fail, and --input equal to --output destroys the input
secret list reports the time of the listing as every secret's creation and last-update time
secret unlocker add pgp without --keyid fails when gpg.conf sets a default-key, because gpgconf prefixes the value with a quote
A vault with corrupt or unreadable metadata is skipped when choosing the next derivation index, so the next vault gets its key
How should vaultik tell an unplugged file:// volume from a new, empty destination?
Plan, per the ruling above (options A and B both; a missing destination directory is an error for a file:// URL only). One PR on next.
**B: a missing file:// destination directory is an…
secret vault import cannot succeed on any vault the tool creates, and the mnemonic help points at secret import
secret generate mnemonic, secret vault list and secret unlocker list print their output to stderr, so it cannot be piped or captured
Removing the current unlocker leaves the vault unable to open through its remaining unlocker
A secret add --force that fails to unlock the vault still leaves a new version behind
remote info counts a file under blobs/ that is not a blob as an orphaned blob
--cron and --quiet do not silence the status lines of prune
snapshot remove reports success for a snapshot that does not exist
remote nuke against a destination it cannot list deletes the local index first
remote nuke leaves a snapshot database without a manifest, and non-blob files under blobs/, and says the store is empty
prune and remote nuke exit 0 when a delete fails, and nuke still says the store is empty
A retention duration of 293 years or more deletes every snapshot
A mnemonic typed with extra whitespace derives a different long-term key, so the vault cannot be recovered with the same words