#856 Enigmail does not decrypt mail

[allo]

Enigmail does not decrypt PGP-Mails anymore. Thunderbird console log:

uncaught exception: subprocess.jsm: caught error:
message: File closed
fileName: resource://enigmail/enigmailprocess_worker_unix.js
lineNumber: 554
column: undefined
stack: getPipe@resource://enigmail/enigmailprocess_worker_unix.js:554:19
write@resource://enigmail/enigmailprocess_worker_common.js:190:18
onmessage/<@resource://enigmail/enigmailprocess_worker_common.js:230:27
onmessage@resource://enigmail/enigmailprocess_worker_common.js:229:3

errorCode: 4286185473

[Patrick Brunschwig]

This is a sign that gpg terminated without closing the pipes properly (in other words, it probably crashed). I'd recommend you kill all of the following processes:
gpg / gpg2, gpg-agent, dirmngr

You may also want to restart Thunderbird.

[J. Vermeulen]

We have the same issue at our company.
Restarting and killing the processes won't work.
We didn't get the error message.

We think it has something to do with the vulnerability fix in version 2.0.6 and onwards.
We rely on encrypted message parts in our workflow.

Version 2.0.5 does work.

[Patrick Brunschwig]

The vulnerability fix in version 2.0.6 will prevent Enigmail from attempting to decrypt at all. You therefore would not see something like the error message above at all.

Possible resolutions for getting messages decrypted are described here:
https://sourceforge.net/p/enigmail/forum/support/thread/03ebee57/

[allo]

I think this should have a useful error message for the user.

A question: I am sending encrypted mails inline from the command line. What do I need to do, so that the gpg command line tool encrypts the messages in a compatible way?

[Patrick Brunschwig]

The question is: why did gpg crash (or exit prematurely)? You may want to check the output from gpg in the Enigmail debug log.

In general, a message is encrpyted like this:

gpg -a -r recipient1 -r recpient2 -r recipient3 --encrypt