#3770: mutt marks armored GPG signed text as encrypted.
----------------------+-------------------------------------------
Reporter: sudoman | Owner: kevin8t8
Type: defect | Status: closed
Priority: major | Milestone:
Component: crypto | Version: 1.5.23
Resolution: fixed | Keywords: gpg signed encrypted pgp mime
----------------------+-------------------------------------------
Changes (by Kevin McCarthy <kevin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [909cf6dd067c07dd0c18ecbbf046c53bddb64afe]:
{{{
#!CommitTicketReference repository=""
revision="909cf6dd067c07dd0c18ecbbf046c53bddb64afe"
Add $pgp_decryption_okay to verify multipart/encrypted are actually
encrypted. (closes #3770)
In pgp classic mode, if the $pgp_decrypt_command generated output, it
assumed the content was encrypted. However, gpg will generate output
even if the block is simply signed and armored text. The problem is
that mutt was then printing mime headers labelling the output as
encrypted text in the ui.
Add a new option, and suggested value of:
set pgp_decryption_okay="^\\[GNUPG:\\] DECRYPTION_OKAY"
If set, the output from the decrypt command will be scanned for this
regexp to confirm an actual decryption occurred.
Note that gpgme already correctly rejects this form of spoofed message.
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3770#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
