password needs to be in uppercase, then lowercase

Bug #808639 reported by Alex Engelmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
New
Undecided
Unassigned

Bug Description

I just started using Deja Dup and have come across a small but annoying bug. I backed up and encrypted my data on an external HDD, but when I try to recover it and put in my password it doesn't work. BUT if I put in my password in all CAPS, then it works long enough to let me choose the date of recovery. But then it fails, saying the pass was incorrect, then asks me for my password again, and this time I need to do it in lowercase. I can't repeat it easily because it seems to only happen when I first install Deja Dup.

I'm using Deja Dup 18.1.1 on Ubuntu 11.04 64bit

Revision history for this message
Michael Terry (mterry) wrote :

After some testing, I think I know what could cause this (now very old) bug. There was a bug in deja-dup/duplicity that allowed for an accidental change in password when making the occasional full backup checkpoint (bug 918489, fixed in deja-dup 34.3).

Here's how this would be reproduced, using deja-dup <= 34.2:
- Create a new backup with password 'a'
- Keep backing up until deja-dup decides to make a new backup. Then either have a different password saved in gnome-keyring or enter a different password when it prompts. Say, 'b'
- Now you have two backup chains with different passwords, but deja-dup will keep adding new backups.
- Until either your cache gets blown away or deja-dup decides to do its every-two-months backup-validation check. (Or heaven forbid, your hard drive gets blown away and you need to restore.)
- When either happens, duplicity will try to download the encrypted manifest files for all the backups and deja-dup will prompt you for the decryption password.
- If you enter 'a', it will choke on your second backup and show the password prompt again. If you enter 'b' it will choke on the first. Thus you get eternal backup prompts.

The only way to recover is to blow away older backups (or the whole thing) and start over. If you were trying to restore, your files can be manually recovered using duplicity though.

Anyway. That's my research into what this bug was likely about. I'll mark it as a dup of bug 918489 (which has been fixed for a while).

In your case, I'm guessing you had caps-lock on once? And then deja-dup/duplicity were sometimes decrypting one backup and sometimes the other? I'm not sure. But our support for these cases has improved, and please open a new bug if you see this behavior again. Thanks!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.