#3808: mutt-1.5.23.1: 'Invalid value passed to IPC'
---------------------+----------------------
Reporter: wiz | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.5.23
Resolution: | Keywords:
---------------------+----------------------
Comment (by cooler):
I ran into this bug, too. It occurs when mutt+gpgme tries to verify
a non-detached S/MIME signature (e.g. MS Outlook produces non-detached
signatures when sending a signed + encrypted message).
I had a look at function decrypt_part in crypt-gpgme.c. It uses a hack
for non-detached signatures. It first tries to decrypt the body data
by calling [[BR]]
'gpgme_op_decrypt (ctx, ciphertext, plaintext)'. [[BR]]
This throws an error if the data is signed and [[BR]]
'gpgme_op_verify (ctx, ciphertext, NULL, plaintext)'[[BR]]
is called. This function throws the error 'Invalid value passed to IPC'.
It appears that the gpgme context 'ctx' gets sort of corrupted by the
first
function call. The attached patch releases and creates a new context
before
calling 'gpgme_op_verify'. This solved the problem for me.
I don't know gpgme, so I don't know if this is actually a bug in gpgme
or in mutt.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3808#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
