search

flathub / org.gnome.DejaDup

https://flathub.org/apps/details/org.gnome.DejaDup
6 stars 2 forks source link

gpg: WARNING: message was not integrity protected #17

Open adamlove86 opened 2 years ago

adamlove86 commented 2 years ago

Hi there, for some reason, recent backups have stopped - perhaps after a restore, but I'm not completely sure.

I'm backing up to a hard drive on local network via SMB.

Error as follows:

GPGError: GPG Failed, see log below: ===== Begin GnuPG log ===== gpg: AES256 encrypted data gpg: encrypted with 1 passphrase gpg: block_filter 0x0000557e389a2280: read error (size=14544,a->size=14544) gpg: block_filter 0x0000557e389a2f50: read error (size=14182,a->size=14182) gpg: WARNING: message was not integrity protected gpg: block_filter: pending bytes! gpg: block_filter: pending bytes! ===== End GnuPG log =====

Perhaps a simple encryption error - I can't seem to find anything related to DejaDup and this issue with dr google unfortunately. Any help would be greatly appreciated! Many thanks.

mikix commented 2 years ago

Hello! Thanks for the report, and sorry that Deja Dup is giving you trouble.

The "read error" looks like the notable error fragment. So either there was an I/O issue or maybe the file got "corrupted" somehow (interrupted during transfer maybe, or something else gone wrong). In those case, gpg can give a wide variety of answers. That's my guess at what's happening here.

It's annoying that we don't seem to print which file is causing the problem? Maybe I should write a patch for duplicity around better debugging messages there.

Is it easy for you to examine the files on the smb server? You could try to manually decrypt them to see which file it is, with something like: gpg --decrypt duplicity-xxx.difftar.gpg > /dev/null -- that would maybe narrow down which file is causing the issue.

bristow commented 1 year ago

Hi, i have the same trouble !

I ran the command on the last 3 files, and here's what I got back. No problems, it seems... 

bristow@Sauvegardes:~/sauve_desktop$ gpg --decrypt duplicity-inc.20231106T082814Z.to.20231107T181055Z.vol1.difftar.gpg > /dev/null

gpg: AES256.CFB encrypted data
gpg: encrypted with 1 passphrase

bristow@Sauvegardes:~/sauve_desktop$ gpg --decrypt duplicity-inc.20231106T082814Z.to.20231107T181055Z.vol2.difftar.gpg > /dev/null

gpg: AES256.CFB encrypted data
gpg: encrypted with 1 passphrase

bristow@Sauvegardes:~/sauve_desktop$ gpg --decrypt duplicity-inc.20231106T082814Z.to.20231107T181055Z.vol3.difftar.gpg > /dev/null

gpg: AES256.CFB encrypted data
gpg: encrypted with 1 passphrase

Is there anything else I can test?

mikix commented 1 year ago

Sorry, I know this isn't super helpful, but I would try it on all the files next then... Try to find if any of them are "broken" - it might help to know which snapshot is broken?

Alternatively, you can start backing up to a new folder to start fresh. But this error doesn't really inspire confidence, I know.