Re: please explain purpose of pgp_decode_command/pgp_good_sign

[seberino@xxxxxxxxxxxxxxx]

Dave

Thanks for the email.  I appreciate your help.

> > There is a pgp_decrypt_command so decode does NOT mean decryption.
>
> However, you need to decode the PGP signature if you hope to be able to
> verify anybody's signature (including your own).

So to "decode" just means parsing the signature and other housekeeping duties???
Why do we need a variable to tweak this behavior then??  I'm guessing
that most people probably don't change this?

> > Also, what is need for pgp_good_sign??
>
> pgp_good_sign is useful to set if your PGP/GPG return code is bogus.

I read the part below too.  If the return code is bogus then that is
a fault of the PGP/GPG app not mutt.  It seems another approach could have been
for mutt to insist the PGP/GPG fix the return code if it is broken
rather than trying to work around the bug.

Are there some cases where the return code is different for good reason
and we DON'T want to modify it??

> Here's what TFM has to say about it (from section 6.3: Configuration
> variables):
>
> pgp_good_sign
>
> Type: regular expression
> Default: ""
>
> If you assign a text to this variable, then a PGP signature is only considered
> verified if the output from $pgp_verify_command contains the text. Use this
> variable if the exit code from the command is 0 even for bad signatures.

Thanks again,

Chris