Say plainly when the private key cannot decrypt a snapshot (closes #427) #448

Merged
clawbot merged 1 commits from issue-427-wrong-key-error into next 2026-11-11 05:24:30 +01:00
1 Commits
Author SHA1 Message Date
sneak 6120522fff Say plainly when the private key cannot decrypt a snapshot (closes #427)
check / check (push) Successful in 9m20s
Restore and deep verify now report "cannot decrypt this snapshot: the
private key in VAULTIK_AGE_SECRET_KEY is not one of the keys the backup
was encrypted to", naming the key source like the invalid-key error.
The doubled "creating decryption reader" prefix and the outer
"downloading snapshot database" / "failed to decrypt database" prefixes
are gone for this case.

A blob the key cannot decrypt, such as one stored before the key was
added as a recipient, now reports "cannot decrypt this blob: the
private key in VAULTIK_AGE_SECRET_KEY is not one of the keys the blob
was encrypted to" after the file and blob it belongs to.

Model: opus-5-5
2026-11-11 04:05:37 +00:00