Re: [Duplicity-talk] Sign-key verification with long fingerprints

[Kenneth Loafman]

Well, it looks like duplicity is only passing the last 8 chars of the sign key, not the longer forms.  The encrypt key is passed unchanged, so the longer forms get passed.

...Ken

On Thu, Nov 17, 2016 at 2:39 PM, Mark Grandi <address@hidden> wrote:

This is indeed a bug, i've run into this before. It seems that it saves whatever you pass in to the duplicity script, but it doesn't do what gpg does and try and expand that to a unique identifier. the work around is to ensure that you pass the long ID to the backup command and not the shortened one

~Mark 

On Nov 17, 2016, at 12:20, Kenneth Loafman via Duplicity-talk <address@hidden> wrote:

Try the verify with 349A3434 as the sign key.  It should work.

...Ken

On Thu, Nov 17, 2016 at 12:25 PM, Richard McGraw via Duplicity-talk <address@hidden> wrote:

Hello,

I tried to verify a backup signed with --sign-key <40-digit-hex-string>

duplicity responds with:
Volume was signed by key 349A3434, not
123434343434343C3434343434343734349A3434

Does it imply that signature verification was skipped ? If yes, it
looks like a bug.

--
 Richard

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk