I manage my backups with duply. Today I wanted to fetch some backuped files from an old machine that got lost on my current machine. Unfortunately I got the error that the storage was signed with another key than the key which was autoselected by duply:

Autoset found secret key of first GPG_KEY entry 'B8C46F4D410B8E334BBA1ECA68D101873E261004' for signing.
Datenträger wurde von Schlüssel 68D101873E261004, anstatt von B8C46F4D410B8E334BBA1ECA68D101873E261004 unterschrieben

(sorry for the 2. message in German but it says what I've just described)

The curious thing is that I am convinced that it is the same key. First, I haven't changed any key duply copied into the profile folder when I created the profile. Second, the numbers of the signing key used by the storag (first key number) is just the last part of the key that was autoselected by duply from the profile folder. Thus, I do not understand what really is happening here.

The keys which were stored by duply in the profile folder during profile generation look like this:

$ ls

which looks kind of redundant as well.

In my duply profile config, it says


Another thing is, that I did not have any trouble when I used the setup the last time and since then I haven't changed anything manually


duplicity, run by duply, was never prepared for the fact that keys may be identified by more than one identifier.

you are right, it complains about the correct key. that shouldn't be a showstopper and only a warning. if you want to work around it, simply set the signing key in it's short form in the duply config and the warning will disappear.


| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.