I think this has gotten even worse in duplicity. I believe this used to only affect full backups. But now it seems to affect incremental backups too.
I've attached a simple reproduction script. It basically just does: PASSPHRASE=one duplicity full /tmp/testdir file://$DIR PASSPHRASE=two duplicity /tmp/testdir file://$DIR Although the second duplicity run complains about a bad password, it will still continue and make an incremental backup with a different passphrase than the full volumes. Tested with duplicity 0.7.18.2. I've worked around this behavior in deja-dup 39.1. ** Attachment added: "repro.sh" https://bugs.launchpad.net/duplicity/+bug/918489/+attachment/5253715/+files/repro.sh ** Summary changed: - duplicity allows bad passphrase on full backup if archive cache exists + duplicity allows a new, different passphrase if an archive cache exists -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows a new, different passphrase if an archive cache exists To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
