#3881: GPGME returns success even if it fails to invoke gpg2
---------------------+----------------------
Reporter: tamo | Owner: mutt-dev
Type: defect | Status: closed
Priority: major | Milestone:
Component: crypto | Version: 1.7.0
Resolution: fixed | Keywords: gpgme
---------------------+----------------------
Changes (by Kevin McCarthy <kevin@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"8963e77577adf7812a8b74fc9fa78d9afb4412c2"
6804:8963e77577ad]:
{{{
#!CommitTicketReference repository=""
revision="8963e77577adf7812a8b74fc9fa78d9afb4412c2"
Ensure signatures exist when verifying multipart/signed emails. (closes
#3881).
TAKAHASHI Tamotsu reported that when gpg2 isn't in PATH, the
gpgme_op_verify() won't return an error, but instead will return a
result with no signatures.
verify_one() was only returning an error if a signature actually
failed, so in this case the function was defaulting to returning
success.
Other callers of gpgme_op_verify() check to make sure the
result->signatures exist before processing signatures. Add a check
for verify_one() too.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3881#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
