Re: duply/duplicity seems to explode with GnuPG 2.1.21

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: duply/duplicity seems to explode with GnuPG 2.1.21

duplicity-talk mailing list
Hello,

I have the same issue. This is a bug that has been introduced in GnuPG
2.1.21. GnuPG returns an error code, even though the signing operation
was successful. The problem has been fixed already in git [1]. Until
2.1.22 is released, I think it's best to downgrade to 2.1.20 (and
convert your keys to the new keyring format if not yet done, to avoid
the corrupting bug in 2.1.19...)

By the way, this bug would not occur if duplicity selected the signing
key with --local-user instead of --default-key. This is better anyway
(if a explicit signing key is set in duplicity) because gpg continues
if the key specified by --default-key is not available. So it could
happen that the backups are signed with another key unintentionally.

[1] https://dev.gnupg.org/rGa8dd96826f8484c0ae93c954035b95c2a75c80f2 

Best,
Tim

_______________________________________________
Duplicity-talk mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/duplicity-talk