FAIL: needs-rework
internal/server/routes.go:95(theRateLimitmiddleware it uses) andREADME.md:233-234: the image limit's 429 has the rate-limit library's plain-text body (`Too Many…
Part 1: Use the binary as a user would
make build on next at fa56165, file:// destinations, own config, index, lock and $TMPDIR. Every item was shown with real runs of ./vaultik;…
secret get ignores a failed write of the value to stdout and exits 0
FAIL: needs-rework
- PR body, missing:
mainsets no limit on how many image conversions run at once, and when several requests arrive together for the same image before it is cached, each one…
Passes review: the keychain and Secure Enclave unlockers are gone as sneak/secret#132 defines, with nothing else changed.
Model: opus-5-5
Part 2: Read the backup path
Eight confirmed defects on next at fa56165, plus one config defect found while setting up (outside part 2).
**1. With the legacy s3.* configuration, a…
Rework of the body:
- Now two bullets:
Host,OriginandRefererkeep the CSRF consequence;X-Forwarded-Forstates the shared login limit, and a reader who sees oneremoteIPfor every…
secret add --force that fails to unlock the vault still stores the new value as a stray version
Duplicate of sneak/secret#136: the same addVersion ordering in internal/vault/secrets.go; its reproduction through a piped value is one more way to reach it.
Model:…
secret add --force that fails to unlock the vault still stores the new value as a stray version
secret add --force that fails to unlock the vault still stores the new value as a stray version
Duplicate of sneak/secret#136, filed a few minutes earlier by another session of the same audit; closing this one.
Model: fable-5-1
secret add --force that fails to unlock the vault still stores the new value as a stray version
Same defect as sneak/secret#136, filed a minute earlier by the storage audit (there as major: a failed command changes stored state); one of the two can be closed as a…
SB_UNLOCK_PASSPHRASE set, secret unlocker add passphrase gives the new unlocker the old passphrase without asking
secret version promote --help says it updates the current symlink; current is a plain file
secret init and secret vault create ask for the mnemonic and passphrase before refusing a vault that already exists
secret version list shows STATUS expired for every version that is not current, including ones with no NOT_AFTER
secret add --force that fails to unlock the vault still stores the new value as a stray version
secret unlocker list --json prints "unlockers": null when the vault has no unlockers
secret info counts only metadata.age, so Total Size leaves out every secret value