duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] volume was signed by key 25B2B3952629147C, not 2629


From: Tapio Sokura
Subject: Re: [Duplicity-talk] volume was signed by key 25B2B3952629147C, not 2629147C
Date: Fri, 30 Mar 2018 00:18:59 +0300
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

Hello,

On 29 Mar 2018 23:26, Jelle de Jong via Duplicity-talk wrote:
Volume was signed by key 25B2B3952629147C, not 2629147C

I don't know why it is changing the key length and how to get rid of the message and decrypt my backup?

The key is most probably the same one in both cases, it's just a question of how the key is referenced. In PGP the traditional way to refer to keys has been to use the last 32 bits of the fingerprint, i.e. 8 hexadecimal characters. The other format lately gaining popularity is to use the last 64 bits of the fingerprint, so 16 hexadecimal characters.

You might want to check your gpg.conf, whether it has a setting named "keyid-format" in there. If it's "short", then 32 bit key ids are used, if "long" 64 bit key ids are used. Try switching the setting to the other if the one already there isn't working. If there's no keyid-format setting, try each variant.

sec   rsa2048 2017-04-04 [SC]
       04CF6921CC8D454A45A5FD3625B2B3952629147C
uid           [  full  ] snip
ssb   rsa2048 2017-04-04 [E]

This should be the key used, compare the last hexadecimal digits of the fingerprint.

  Tapio



reply via email to

[Prev in Thread] Current Thread [Next in Thread]