list-current-files fails if sync is needed

Bug #1828869 reported by Mgorse on 2019-05-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Medium
Unassigned

Bug Description

If a sync is needed, then list-current-files now fails as follows:

GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: AES encrypted data
gpg: gcry_kdf_derive failed: Invalid data
gpg: encrypted with 1 passphrase
gpg: decryption failed: No secret key
===== End GnuPG log =====

Gpg is complaining because it is not given a passphrase, but the real issue seems to be that the collection is now initialized before the sync, rather than after it, and it is not properly updated, so duplicity looks for a sigtar.gpg file and tries to decrypt it even though it has already been decrypted and stored locally as part of the sync.

Also, the following check can cause a traceback on python 3, since sometimes a ParseResults sets a time, rather than start_time and end_time:
+ return parsed.end_time >= target_chain.start_time and \
+ parsed.start_time <= target_chain.end_time

Since parsed.start_time and parsed.end_time can be None, it looks as though the code may also behave incorrectly on python 2.

Related branches

Changed in duplicity:
status: New → In Progress
importance: Undecided → Medium
milestone: none → 0.8.00
Changed in duplicity:
status: In Progress → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers