Re: [Duplicity-talk] duply/duplicity seems to explode with GnuPG 2.1.21

[Philip Jocks]

Pretty strange, gpg seems to be working "fine", it just seems to spew quite a 
lot of error/debug messages and maybe the exit codes are unexpected.
Setting GPG_TEST=disabled, duply profilename fetch ... ... works also fine, but 
duply thinks differently:

08:41:15.000 Task 'FETCH' failed with exit code '22'.
--- Finished state FAILED 'code 22' at 08:41:15.000 - Runtime 00:00:02.000 ---

I don't know what changed, but a machine running GnuPG 2.1.20 works fine.

> Am 17.05.2017 um 20:54 schrieb Philip Jocks via Duplicity-talk 
> <address@hidden>:
> 
> Hej,
> 
> I upgraded to GnuPG 2.1.21 today and duply/duplicity stopped working since 
> then.
> The selftest fails:
> 
> --
> Start duply v1.10.1, time is 2017-05-17 20:51:15.
> Using profile '/root/.duply/profilename'.
> Using installed duplicity version 0.7.12, python 2.7.13, gpg 2.1.21 (Home: 
> /root/.gnupg), awk 'awk version 20121220 (FreeBSD)', grep 'grep (GNU grep) 
> 2.5.1-FreeBSD', bash '4.4.12(2)-release (amd64-portbld-freebsd10.3)'.
> Autoset found secret key of first GPG_KEY entry 'AAAAAAAA' for signing.
> Checking TEMP_DIR '/tmp' is a folder (OK)
> Checking TEMP_DIR '/tmp' is writable (OK)
> Test - Encrypt to 'AAAAAAAA','BBBBBBBB' & Sign with 'AAAAAAAA' (FAILED)
> 
> Sorry. A fatal ERROR occured:
> 
> Encryption failed (Code 2).
> gpg: Warning: using insecure memory!
> gpg: error getting version from 'scdaemon': Not supported
> [GNUPG:] CARDCTRL 6
> gpg: using "AAAAAAAA" as default secret key for signing
> [GNUPG:] KEY_CONSIDERED CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCAAAAAAAA 2
> [GNUPG:] KEY_CONSIDERED DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBBBBBBBB 0
> [GNUPG:] KEY_CONSIDERED DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDBBBBBBBB 0
> [GNUPG:] KEY_CONSIDERED CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCAAAAAAAA 0
> [GNUPG:] KEY_CONSIDERED CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCAAAAAAAA 0
> [GNUPG:] BEGIN_SIGNING H2
> [GNUPG:] SIG_CREATED S 1 2 00 1495047075 
> CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCAAAAAAAA
> [GNUPG:] BEGIN_ENCRYPTION 2 9
> [GNUPG:] END_ENCRYPTION
> 
> Hint:
>  This error means that gpg is probably misconfigured or not working 
>  correctly. The error message above should help to solve the problem.
>  However, if for some reason duply should misinterpret the situation you 
>  can define GPG_TEST='disabled' in the conf file to bypass the test.
>  Please do not forget to report the bug in order to resolve the problem
>  in future versions of duply.
> 
> --
> 
> and when I set GPG_TEST=disabled, this is what duply profilename backup dies 
> with:
> 
> --
> ...
> GPG error detail: Traceback (most recent call last):
>  File "/usr/local/bin/duplicity", line 1546, in <module>
>    with_tempdir(main)
>  File "/usr/local/bin/duplicity", line 1540, in with_tempdir
>    fn()
>  File "/usr/local/bin/duplicity", line 1391, in main
>    do_backup(action)
>  File "/usr/local/bin/duplicity", line 1522, in do_backup
>    incremental_backup(sig_chain)
>  File "/usr/local/bin/duplicity", line 671, in incremental_backup
>    globals.backend)
>  File "/usr/local/bin/duplicity", line 432, in write_multivol
>    globals.volsize)
>  File "/usr/local/lib/python2.7/site-packages/duplicity/gpg.py", line 376, in 
> GPGWriteFile
>    file.close()
>  File "/usr/local/lib/python2.7/site-packages/duplicity/gpg.py", line 261, in 
> close
>    self.gpg_failed()
>  File "/usr/local/lib/python2.7/site-packages/duplicity/gpg.py", line 246, in 
> gpg_failed
>    raise GPGError(msg)
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: error getting version from 'scdaemon': Not supported
> gpg: using "AAAAAAAA" as default secret key for signing
> ===== End GnuPG log =====
> 
> 
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: error getting version from 'scdaemon': Not supported
> gpg: using "AAAAAAAA" as default secret key for signing
> ===== End GnuPG log =====
> 
> 20:36:34.000 Task 'BKP' failed with exit code '31'.
> --- Finished state FAILED 'code 31' at 20:36:34.000 - Runtime 00:00:22.000 ---
> 
> --- Start running command POST at 20:36:34.000 ---
> Skipping n/a script '/root/.duply/profilename/post'.
> --- Finished state OK at 20:36:34.000 - Runtime 00:00:00.000 ---
> --
> 
> We're using FreeBSD and build gnupg without the scdaemon stuff. Using gpg to 
> encrypt and decrypt on this machine works fine, though.
> 
> Does this ring a bell anywhere?
> 
> Cheers,
> 
> Philip
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk