#3828: mutt-1.6.0: send fails after canceling pgp with pgp_autoinline set
----------------------+----------------------
Reporter: william | Owner: kevin8t8
Type: defect | Status: closed
Priority: major | Milestone:
Component: IMAP | Version:
Resolution: fixed | Keywords:
----------------------+----------------------
Changes (by Kevin McCarthy <kevin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a6a4d6ed0f19149e1ae54a479bdafaa925ddf078"]:
{{{
#!CommitTicketReference repository=""
revision="a6a4d6ed0f19149e1ae54a479bdafaa925ddf078"
Fix mutt_protect() when INLINE is set. (closes #3828)
The oppenc changes allow security bits to be set even when not
encrypting or signing (for instance, OPPENCRYPT and INLINE).
mutt_protect() assumed that if INLINE is set, then either ENCRYPT or
SIGN must also be set. Specifically, it would end up inline-signing
the message even though neither was set.
Ensure mutt_protect() is a noop if neither SIGN or ENCRYPT are set.
In ci_send_message(), check for sign or encrypt before calling the
crypt_get_keys() / mutt_protect() block, and also in the fcc section
(since clear_content would be NULL if not).
The second change to the fcc part is somewhat redundant, but better to
be explicit and avoid the case where the subtype is somehow
"encrypted" or "signed" even though msg->security wasn't set thus.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3828#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
