Deja Dup restore wizard lacking automatic integrity verification option

When restoring files with Deja Dup’s restore wizard on KDE Neon, the operation completes without any automatic check that the recovered data matches the original backup. Users must manually compute checksums or compare files, which is impractical for large or encrypted datasets and leaves silent corruption undetected. The goal is to have the restore process optionally verify integrity after the files are written, while respecting backup encryption and avoiding unnecessary overhead for users who do not need verification. Considerations include how to handle passphrase‑protected backups without exposing the secret, whether to verify the entire restore set or a statistical sample, and how to expose the result without breaking the wizard’s flow.

• Should Deja Dup add a toggle in the restore wizard to enable automatic post‑restore checksum verification?
• How can the verification be performed on encrypted backups without requiring the user to re‑enter the passphrase in plain text?
• What verification scope (full file‑by‑field hash vs sampled blocks) offers a reasonable balance between confidence and performance for typical desktop users?