Treat decryption failure as a read error? about scat HOT 1 OPEN

My response:

Ah, yes... So, in fact, uparity supports both missing files and integrity check failures.

However in this case, with gpg before uchecksum, you don't get an integrity check failure because gpg fails first due to invalid crypted data.

Indeed, we have to checksum before gpg (and in the restore script, uchecksum after gpg), because gpg generates different crypted data every time, for identical input data.

The consequence is that changing data on remotes results in failed decompression rather than failed integrity check (what I wanted initially, before realizing gpg generates different data every time).

So that's a very good point. I don't know what to do, if considering any error as potentially recoverable by uparity, not just integrity check or missing data 🤔 I'll leave the ticket open until deciding.

from scat.