#77 base64-encoded pgp/mime mails fail to decrypt

open
nobody
None
1.4.1
Major
2015-02-20
2012-08-10
No

Bug 24879 migrated from Mozdev.org

The attached email is shown as empty after decryption, although its content can
be decrypted properly on the commandline. The decryption result can also be
shown correctly in Thunderbird with File>Open File.

==== enigdbug.txt content follows ====

2012-05-02 21:23:42.961 [DEBUG] enigmail.js: Logging debug output to
e:\debug\\enigdbug.txt
2012-05-02 21:23:42.962 [DEBUG] enigmail.js: Enigmail version 1.4.1
2012-05-02 21:23:42.963 [DEBUG] enigmail.js: OS/CPU=Windows NT 5.1
2012-05-02 21:23:42.964 [DEBUG] enigmail.js: Platform=Windows
2012-05-02 21:23:42.965 [DEBUG] enigmail.js: composeSecure=true
2012-05-02 21:23:42.966 [DEBUG] enigmail.js: Enigmail.initialize: Ec.envList =
ALLUSERSPROFILE=C:\Documents and Settings\All Users,APPDATA=C:\Documents and
Settings\admin\Application Data,COMMONPROGRAMFILES=C:\Program Files\Common
Files,COMSPEC=C:\WINDOWS\system32\cmd.exe,HOMEDRIVE=C:,HOMEPATH=\Documents and
Settings\admin,PATH=C:\Program Files\Mozilla
Thunderbird;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem,PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH,PROGRAMFILES=C:\Program
Files,SYSTEMDRIVE=C:,SYSTEMROOT=C:\WINDOWS,TEMP=C:\DOCUME~1\admin\LOCALS~1\Temp,TMP=C:\DOCUME~1\admin\LOCALS~1\Temp,USERPROFILE=C:\Documents
and Settings\admin,WINDIR=C:\WINDOWS
2012-05-02 21:23:42.968 [CONSOLE] EnigmailAgentPath=C:\Program
Files\GNU\GnuPG\gpg.exe

2012-05-02 21:23:42.970 [DEBUG] enigmail.js: Enigmail.setAgentPath: calling
subprocess with 'C:\Program Files\GNU\GnuPG\gpg.exe'
2012-05-02 21:23:43.069 [CONSOLE] enigmail> C:\Program Files\GNU\GnuPG\gpg.exe
--version --version --batch --no-tty --charset utf-8 --display-charset utf-8
2012-05-02 21:23:43.070 [CONSOLE] gpg (GnuPG) 1.4.12
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: C:/Documents and Settings/admin/Application Data/gnupg
Untersttzte Verfahren:
ff. Schlssel: RSA, RSA-E, RSA-S, ELG-E, DSA
Verschl.: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, 
           CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Komprimierung: nicht komprimiert, ZIP, ZLIB, BZIP2

2012-05-02 21:23:43.071 [DEBUG] enigmail.js: detected GnuPG version '1.4.12'
2012-05-02 21:23:43.072 [DEBUG] enigmail.js: detectGpgAgent
2012-05-02 21:23:43.073 [DEBUG] enigmail.js: detectGpgAgent: no GPG_AGENT_INFO
variable set
2012-05-02 21:23:43.074 [DEBUG] enigmail.js: detectGpgAgent - gpg 1.x found
2012-05-02 21:23:43.074 [DEBUG] enigmail.js: detectGpgAgent: GPG_AGENT_INFO=''
2012-05-02 21:23:43.075 [DEBUG] enigmailCommon.jsm: stillActive: 
2012-05-02 21:23:43.076 [DEBUG] enigmail.js: Enigmail.initialize: END
2012-05-02 21:23:43.077 [DEBUG] enigmailCommon.js: getService: 1.4.1
2012-05-02 21:23:43.078 [DEBUG] enigmailCommon.jsm: getVersion
2012-05-02 21:23:43.078 [DEBUG] enigmailCommon.jsm: installed version: 1.4.1
2012-05-02 21:23:43.079 [DEBUG] enigmailMessengerOverlay.js: messageDecryptCb:
2012-05-02 21:23:43.080 [DEBUG] enigmailMessengerOverlay.js: header
content-type: multipart/encrypted; boundary="nextPart1669343.XXflNmAgI4";
protocol="application/pgp-encrypted"
2012-05-02 21:23:43.081 [DEBUG] enigmailMessengerOverlay.js: header
content-transfer-encoding: base64
2012-05-02 21:23:43.082 [DEBUG] enigmailMessengerOverlay.js: header
x-enigmail-version: 
2012-05-02 21:23:43.082 [DEBUG] enigmailMessengerOverlay.js: header
x-pgp-encoding-format: 
2012-05-02 21:23:43.083 [DEBUG] enumerateMimeParts:  - multipart/encrypted;
boundary="nextPart1669343.XXflNmAgI4"; protocol="application/pgp-encrypted"
2012-05-02 21:23:43.084 [DEBUG] enumerateMimeParts: 1 - multipart/encrypted;
boundary="nextPart1669343.XXflNmAgI4"; protocol="application/pgp-encrypted"
2012-05-02 21:23:43.085 [DEBUG] enumerateMimeParts: 1.1 -
application/pgp-encrypted
2012-05-02 21:23:43.086 [DEBUG] enumerateMimeParts: 1.2 -
application/octet-stream
2012-05-02 21:23:43.087 [DEBUG] enigmailMessengerOverlay.js: embedded objects:
1.1 / 
2012-05-02 21:23:43.089 [DEBUG] enigmailMessengerOverlay.js:
multipart/encrypted
2012-05-02 21:23:43.091 [DEBUG] enigmail.js: Enigmail.mimeInitialized: false
2012-05-02 21:23:43.093 [DEBUG] enigmailMessengerOverlay.js:
enigMimeInitialize() - loading enigmail:dummy ...
2012-05-02 21:23:43.093 [DEBUG] enigmailCommon.jsm: getFrame: name=messagepane
2012-05-02 21:23:43.095 [DEBUG] enigmail.js: EnigmailProtocolHandler.newURI:
aSpec='enigmail:dummy'
2012-05-02 21:23:43.096 [DEBUG] enigmail.js:
EnigmailProtocolHandler.newChannel: URI='enigmail:dummy'
2012-05-02 21:23:43.097 [DEBUG] enigmailCommon.jsm: newStringChannel
2012-05-02 21:23:43.098 [DEBUG] enigmailCommon.jsm: newStringChannel - done
2012-05-02 21:23:43.101 [DEBUG] enigmailMessengerOverlay.js: messageFrameUnload
2012-05-02 21:23:43.102 [DEBUG] enigmailMsgHdrViewOverlay.js:
this.messageUnload
2012-05-02 21:23:43.118 [DEBUG] enigmailMessengerOverlay.js: *****enigMimeInit
2012-05-02 21:23:43.119 [DEBUG] enigmailMessengerOverlay.js: *****enigMimeInit:
handlePGPMime=true
2012-05-02 21:23:43.120 [DEBUG] enigmail.js: Enigmail.mimeInitialized: true
2012-05-02 21:23:43.121 [DEBUG] enigmailMessengerOverlay.js: *****enigMimeInit:
RELOADING MESSAGE
2012-05-02 21:23:43.122 [DEBUG] enigmailMessengerOverlay.js:
this.messageReload: false
2012-05-02 21:23:43.150 [DEBUG] enigmailMessengerOverlay.js: messageFrameUnload
2012-05-02 21:23:43.151 [DEBUG] enigmailMessengerOverlay.js: messageCleanup
2012-05-02 21:23:43.152 [DEBUG] enigmailMessengerOverlay.js:
setAttachmentReveal
2012-05-02 21:23:43.157 [DEBUG] enigmailMsgHdrViewOverlay.js:
_listener_onStartHeaders
2012-05-02 21:23:43.158 [DEBUG] enigmailCommon.jsm: getFrame: name=messagepane
2012-05-02 21:23:43.160 [DEBUG] enigmailMsgHdrViewOverlay.js: msgFrame=[object
Window]
2012-05-02 21:23:43.161 [DEBUG] enigmailMsgHdrViewOverlay.js:
enigmailPrepSecurityInfo
2012-05-02 21:23:43.193 [DEBUG] enigmailMsgHdrViewOverlay.js:
_listener_onEndHeaders
2012-05-02 21:23:43.207 [DEBUG] enigmailMessengerOverlay.js: messageDecrypt:
[object Event]
2012-05-02 21:23:43.214 [DEBUG] enigmailCommon.jsm: dispatchEvent f=
2012-05-02 21:23:43.216 [DEBUG] enigmailCommon.jsm: dispatchEvent running
mainEvent
2012-05-02 21:23:43.217 [DEBUG] enigmailMessengerOverlay.js: messageDecryptCb:
2012-05-02 21:23:43.218 [DEBUG] enigmailMessengerOverlay.js: header
content-type: multipart/encrypted; boundary="nextPart1669343.XXflNmAgI4";
protocol="application/pgp-encrypted"
2012-05-02 21:23:43.219 [DEBUG] enigmailMessengerOverlay.js: header
content-transfer-encoding: base64
2012-05-02 21:23:43.219 [DEBUG] enigmailMessengerOverlay.js: header
x-enigmail-version: 
2012-05-02 21:23:43.220 [DEBUG] enigmailMessengerOverlay.js: header
x-pgp-encoding-format: 
2012-05-02 21:23:43.221 [DEBUG] enumerateMimeParts:  - multipart/encrypted;
boundary="nextPart1669343.XXflNmAgI4"; protocol="application/pgp-encrypted"
2012-05-02 21:23:43.221 [DEBUG] enumerateMimeParts: 1 - multipart/encrypted;
boundary="nextPart1669343.XXflNmAgI4"; protocol="application/pgp-encrypted"
2012-05-02 21:23:43.222 [DEBUG] enigmailMessengerOverlay.js: embedded objects:
1 / 
2012-05-02 21:23:43.223 [DEBUG] enigmailMessengerOverlay.js:
multipart/encrypted
2012-05-02 21:23:43.224 [DEBUG] enigmail.js: Enigmail.mimeInitialized: true
2012-05-02 21:23:43.225 [DEBUG] enigmail.js: Enigmail.mimeInitialized: true
2012-05-02 21:23:57.368 [DEBUG] enigmailMsgHdrViewOverlay.js:
this.hdrViewUnLoad
2012-05-02 21:23:57.389 [DEBUG] enigmailMessengerOverlay.js: messageFrameUnload
2012-05-02 21:23:57.390 [DEBUG] enigmailMessengerOverlay.js: messageCleanup
2012-05-02 21:23:57.391 [DEBUG] enigmailMessengerOverlay.js:
setAttachmentReveal
2012-05-02 21:23:57.392 [DEBUG] enigmailMsgHdrViewOverlay.js:
this.messageUnload
2012-05-02 21:23:57.520 [DEBUG] enigmail.js: Enigmail.observe:
topic='xpcom-shutdown' 
2012-05-02 21:23:57.526 [DEBUG] enigmail.js: Enigmail.finalize:

------- Comment #1 From daniel.hornung@gmx.de 2012-05-02 12:30:15 [reply] -------

Created an attachment (id=7244) [details]
The problematic file

I think this bug is also responsible for a few times when people I know could
not open emails with attachments I sent them, they complained they were empty.

------- Comment #2 From daniel.hornung@gmx.de 2012-05-02 12:30:51 [reply] -------

Created an attachment (id=7245) [details]
The same file, but decrypted on the command line.

------- Comment #3 From Patrick Brunschwig 2012-05-03 09:31:13 [reply] -------

Your suspicion is correct. If the content-transfer-encoding of the top level
MIME part is "base64" then decryption does not work.

------- Comment #4 From Patrick Brunschwig 2012-05-04 07:57:24 [reply] -------

Bug 24878 has been marked as a duplicate of this bug.

------- Comment #5 From Patrick Brunschwig 2012-05-04 07:58:15 [reply] -------

Quoted-Printable in the main MIME part leads to the same result (no surprise).

------- Comment #6 From daniel.hornung@gmx.de 2012-05-04 12:31:04 [reply] -------

(In reply to comment #5)

Quoted-Printable in the main MIME part leads to the same result (no surprise).

This lets me hope for a quick fix for both at once :)

But I guess you noticed that not all quoted-printable messages produce the
problem?

------- Comment #7 From Patrick Brunschwig 2012-05-06 03:48:10 [reply] -------

(In reply to comment #6)

Quoted-Printable in the main MIME part leads to the same result (no surprise).

This lets me hope for a quick fix for both at once :)

There is no quick fix for this, you will have to wait for at least version
1.4.3.

But I guess you noticed that not all quoted-printable messages produce the
problem?

That's in the nature of quoted-printable.

1 Attachments

Related

Bugs: #546
Forum: enigmail unable to decrypt/show mail

Discussion

  • Daniel Hornung

    Daniel Hornung - 2013-02-10

    Any news on this for the current or upcoming versions?

     
  • Ludwig Hügelschäfer

    No real news, but we had an internal discussion. This bug is hard to solve and requires changes in Thunderbird itself, in a code part that Patrick contributed.

    My personal opinion: Specifiying a content-transfer encoding header for a mail that contains only other MIME parts is broken, so a bug should be filed for KMail, too.

     
  • Patrick Brunschwig

    To be precise: according to some RFC (I don't remember which one), it is
    forbidden to specify a transfer encoding on the level of the message itself.

     
  • Teh Hua Ze Brian

    Hi Patrick,

    The transfer encoding rule was forbidden in RFC2045, but it was relaxed in RFC6532.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks