Thanks! I looked for a rest option in the
password command and under Managing Passwords in the wiki, but it did not occur to me to check the
I have added the information to the managing passwords wiki page (BTW: shouldn’t we be talking about pass_phrases_, these days?).
Now, if you don’t mind me asking: what might possibly have led to the password having been changed? I did recently create a new password when I changed my chunk-size to 1M, but I don’t quite understand how that might have cause this issue.
To be concrete: since changing chunk size means to start the backup archive from scratch, I created a new folder in the backend and initiated it with the new chunk size. I did not touch the old backend folder or the preferences for the old backups, I just stopped running them and created a new repository (or rather, started backing up the old one to the new storage). It worked fine for several days, so I can’t really link the issue with the new password. Or why would the
keyring file only be changed several days later? Or changed back several days later?
UPDATE: In the mean time, I did the
duplicacy list -reset-passwords and it worked in the sense that I was able to enter a password and subsequently the backup worked. But I have no idea what I actually did when entering that password. Did I just enter the correct storage password that was already set or did I set a new storage password?
To improve the UX here, I’d suggest to clarify the question that duplicacy issues. Currently it just says
Storage set to <whatever the path>
Enter storage password:
If what you enter here is a new storage password, I think it should say
Enter new storage password:
Enter new storage password (or press *** to quit): (fill in *** as appropriate).