Hello Allison, or anyone else affected, Accepted deja-dup into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/deja- dup/30.0-0ubuntu4.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/918489 Title: duplicity allows bad passphrase on full backup if archive cache exists Status in Déjà Dup: Fix Released Status in Duplicity: New Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Trusty: Fix Committed Status in deja-dup source package in Xenial: Fix Committed Status in deja-dup source package in Yakkety: Fix Committed Bug description: when doing a backup for the first time, dejadup verifies your passphrase by having you enter it twice. on future incremental backups it doesn't need to do this because entering the wrong password will result in the backup failing. with the periodic 'full' backups that happen from time to time, however, any password will be accepted. this can lead to a situation where you accidentally type the wrong password once and are left in a situation where you don't know what you typed and have no way to get your files (or do another incremental backup on top of it). i think this is what happened to me recently. clearly, the fix is to explicitly verify the passphrase is correct when doing a new full backup. this may be a duplicity bug. === Ubuntu deja-dup SRU information === [impact] Users may unwittingly re-set their backup password and not be able to restore their data. [test case] - $ deja-dup-preferences # set up a dummy backup - $ deja-dup --backup # complete first encrypted full backup - $ rename 's/\.2016/\.2000/' /path/to/test/backup/* - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/* - $ deja-dup --backup # second backup, enter the wrong password - $ deja-dup --restore # try to restore with original password [regression potential] Should be limited? The fix is to delete the duplicity cache files, which ought to be safe to delete. It's possible if a full backup is being resumed, we might delete the current progress. That is a better bug to have than this bug, though. A more complicated patch would need to be investigated to prevent that. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
