[issue293] gpgsm debug output in signature

New submission from Bernhard Herzog <[email protected]>:

gpgsm seems to write its debug output into the wrong file in some situations.  I
have a log socket configured for gpgsm and the other backend components to write
to.  Nobody is listening on that socket though.  The agent dutifully writes its
debug output to stderr.

gpgsm doesn't seem to do that and if a default-key is configured in gpgsm.conf,
it writes the debug output into file descriptors used for assuan traffic.  One
result of that is that in mutt the debug output ends up in the signature of
mutlipart/signed messages so that it's not a CMS object anymore.  An attempt to
verify such a signature gives the error:

Error: verification failed: No CMS object

Looking at the decoded signature reveals that it starts with debug info:

gpgsm[17897]: DBG: adding certificates at level 1
gpgsm[17897]: DBG: get_keygrip for public key
gpgsm[17897]: DBG: keygrip= D3 2E 74 97 40 D6 A7 53 99 0E C9 FA 2C 8B 9B 88 81
36 2F B1
gpgsm[17897.0x807ce70] DBG: -> S SIG_CREATED D 1 2 00 20050118T172429
800898435FB955AB40D74F0796D71979CD14F72C
gpgsm[17897]: signature created

----------
assignedto: werner
messages: 1892
nosy: bh, werner
priority: bug
status: unread
title: gpgsm debug output in signature
topic: gpgsm
______________________________________________________
Aegypten issue tracker <[email protected]>
<https://intevation.de/roundup/aegypten/issue293>
______________________________________________________