Re: PGG broken?

[Andreas Seltenreich <andreas+ding@gate450.dyndns.org>]

Marcus Frings schrob:

> * Marcus Frings <iam-est-hora-surgere@despammed.com> wrote:
>
>> 1) When I use the set-policy-url option in my gpg.conf I can't sign
>>    mails anymore ("sign error"). After removing this option I can sign
>>    mails again.

Hmm, did you really get a "sign error" signalled?[1] When I tried to
reproduce it, I got a 'search-failed one from pgg-parse-armor, because
pgg-gpg-sign-region returned successful signing status and an empty
output buffer at the same time.

In my case, GnuPG[2] returned a non-zero exit-status because it couldn't
generate a signature with a policy URL while maintaining PGP
compatibility. Nevertheless, it did the signing without a policy URL
and reported SIG_CREATED.

The non-zero exit status caused the pgg-gpg sentinel to discard the
output, pgg-gpg-sign-region however saw the SIG_CREATED on the
status-fd and returned success despite the discarded output.

Switching PGP-compatibility off via "openpgp" in gpg.conf made the
signing succeed with a policy URL set.

Of course, the underdone error handling is still there, and I wonder
if one should fix it by making the sentinel not discard the output on
non-zero exit status, or forcing pgg-gpg to return failure even if
there might be useful output. Anyone?

regards,
andreas

[1] I'm figuring that the " *MML2015 result*" buffer should have
    popped up then, and the problem with the policy-url option should
    have been obvious. OTOH you might have already disabled PGP
    compatibility, and are experiencing a different bug :-/.

[2] 1.4.1