Running with Enigmail 1.5, Tbird 17.0.2, OS X 10.8.2. PGP/MIME was working fine then stopped. I'm not sure what the failure trigger was, but it may have been one of many Tbird hangs/force-quits. Now, I cannot send anything with PGP/MIME enabled. It fails during encryption with an exception in mimeEncrypt.js. I've reinstalled Tbird, Enigmail, and GPGTools, but the problem persists. I'm at my wits' end. Any ideas what I can do to recover PGP/MIME ability?
Here's the seemingly relevant portion of the debug log:
Manually running gpg with the above args, isolating the args until the culprit is found, I see a "general error" when signing with "--digest-algo sha1". The problem is, my Enigmail is correctly configured with mimeHashAlgorithm set to 0 (let GnuPG decide), so this gpg arg shouldn't be used. How is it being set to sha1?
Last edit: Anonymous 2013-01-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry to hear this. Did you try to clear the cache? If not, please close Thunderbird, go to your users directory, then Library/Caches/Thunderbird/Profiles/<Profile name), delete everythin in there. If that doesn't help, please try a fresh Thunderbird profile.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-12
Yeah, tried both (clearing cache, fresh profile). No change, I'm afraid.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, I agree that "--digest-algo sha1" should not be used in combination with a 3072-bit DSA2 key and will gpg2 cause to fail.
Please use the config-editor of Thunderbird and search for "sha1". If that doesn't give a result, please search for all entries containing "enigmail". Look out for the highlighted entries, these are user-set and not default. Is anything suspicious there?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-12
There are no instances of sha1 and nothing suspicious among user-set options (of which there are only a few benign ones) in the set of enigmail settings. mimeHashAlgorithm is still its default setting of zero, suggesting digest-algo shouldn't be specified at all.
Just in case, here are the non-default enigmail settings:
advancedUser = true
allowEmptySubject = true (testing with non-empty subjects, though)
alwaysTrustSend = false
composeHtmlAlertCount = 1
displaySignWarn = false
keyManShowAllKeys = true
maxIdleMinutes = 0 (I'm using gpg-agent)
useDefaultComment = true
warnGpgAgentAndIdleTime = false
All other enigmail settings are defaults.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I believe that this was fixed on trunk a few days ago. Could you please try a nightly build from http://www.enigmail.net/download/nightly.php and let me know if you still have this issue?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-13
The issue changed with the nightly build (build date: 2013-01-13 version: 1.6a1pre for Mac/Tbird-17). Now, selecting PGP/MIME doesn't fail when sending but doesn't encrypt or sign at all (and has no PGP/MIME components)--it just looks like a plain email.
I bet there is an error message in the Error Console. The Enigmail
version you're using doesn't work with Thunderbird 17. I'll have to talk
to Ludwig ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just tested with the latest nightly build for Mac OS X. You should see the following entry in the error console:
"Native module at path '$Profil_dir/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/platform/Darwin_x86_64-gcc3/components/libenigmime-x86_64-gcc3.dylib' is incompatible with this version of Firefox, has version 18, expected 17."
Sorry for that. I'll have to inspect the build process, I will post again when this is fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-14
You're right, it did. (Sorry it took me so long to confirm.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Build is running, will take 2 to 4 hours. Hope this will fix this issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-14
Thanks so much for your help. You guys have been great.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2013-01-15
I don't know if I was supposed to test "build date: 2013-01-14 version: 1.6a1pre", but it produced the same incompatible error message and the same symptom as the 01-13 one did.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Running with Enigmail 1.5, Tbird 17.0.2, OS X 10.8.2. PGP/MIME was working fine then stopped. I'm not sure what the failure trigger was, but it may have been one of many Tbird hangs/force-quits. Now, I cannot send anything with PGP/MIME enabled. It fails during encryption with an exception in mimeEncrypt.js. I've reinstalled Tbird, Enigmail, and GPGTools, but the problem persists. I'm at my wits' end. Any ideas what I can do to recover PGP/MIME ability?
Here's the seemingly relevant portion of the debug log:
2013-01-12 10:04:47.137 [CONSOLE] enigmail> /usr/local/bin/gpg --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 --digest-algo sha1 -a -t --encrypt --sign --encrypt-to 0x26388C31 -r 0xC377492826388C31 -u 0x26388C31 --use-agent
2013-01-12 10:04:47.143 [DEBUG] enigmail.js: Setting useAgent to true for gpg2 >= 2.0.16
2013-01-12 10:04:47.842 [DEBUG] enigmailCommon.jsm: encryptMessageEnd: uiFlags=9, sendFlags=000000c3, outputLen=1478
2013-01-12 10:04:47.842 enigmailCommon.jsm: parseErrorOutput:
2013-01-12 10:04:47.842 [DEBUG] enigmailCommon.jsm: parseErrorOutput: statusFlags = 00000000
2013-01-12 10:04:47.842 [DEBUG] enigmailCommon.jsm: encryptMessageEnd: command execution exit code: 512
2013-01-12 10:04:49.764 [ERROR] mimeEncrypt.js: caught exception: undefined
Message: 'undefined'
File: undefined
Line: undefined
Stack: undefined
Manually running gpg with the above args, isolating the args until the culprit is found, I see a "general error" when signing with "--digest-algo sha1". The problem is, my Enigmail is correctly configured with mimeHashAlgorithm set to 0 (let GnuPG decide), so this gpg arg shouldn't be used. How is it being set to sha1?
Last edit: Anonymous 2013-01-12
Sorry to hear this. Did you try to clear the cache? If not, please close Thunderbird, go to your users directory, then Library/Caches/Thunderbird/Profiles/<Profile name), delete everythin in there. If that doesn't help, please try a fresh Thunderbird profile.
Yeah, tried both (clearing cache, fresh profile). No change, I'm afraid.
Thanks.
Ok, I agree that "--digest-algo sha1" should not be used in combination with a 3072-bit DSA2 key and will gpg2 cause to fail.
Please use the config-editor of Thunderbird and search for "sha1". If that doesn't give a result, please search for all entries containing "enigmail". Look out for the highlighted entries, these are user-set and not default. Is anything suspicious there?
There are no instances of sha1 and nothing suspicious among user-set options (of which there are only a few benign ones) in the set of enigmail settings. mimeHashAlgorithm is still its default setting of zero, suggesting digest-algo shouldn't be specified at all.
Just in case, here are the non-default enigmail settings:
advancedUser = true
allowEmptySubject = true (testing with non-empty subjects, though)
alwaysTrustSend = false
composeHtmlAlertCount = 1
displaySignWarn = false
keyManShowAllKeys = true
maxIdleMinutes = 0 (I'm using gpg-agent)
useDefaultComment = true
warnGpgAgentAndIdleTime = false
All other enigmail settings are defaults.
Could you please attach a debug log file? Instructions can be found here: http://www.enigmail.net/forum/viewtopic.php?f=10&t=289
sorry, I wanted to write ... a complete debug log file. The interesting stuff for me is earlier than the excerpt you submitted.
You bet!
Last edit: Anonymous 2013-01-13
I believe that this was fixed on trunk a few days ago. Could you please try a nightly build from http://www.enigmail.net/download/nightly.php and let me know if you still have this issue?
The issue changed with the nightly build (build date: 2013-01-13 version: 1.6a1pre for Mac/Tbird-17). Now, selecting PGP/MIME doesn't fail when sending but doesn't encrypt or sign at all (and has no PGP/MIME components)--it just looks like a plain email.
Last edit: Anonymous 2013-01-14
I bet there is an error message in the Error Console. The Enigmail
version you're using doesn't work with Thunderbird 17. I'll have to talk
to Ludwig ...
Just tested with the latest nightly build for Mac OS X. You should see the following entry in the error console:
"Native module at path '$Profil_dir/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/platform/Darwin_x86_64-gcc3/components/libenigmime-x86_64-gcc3.dylib' is incompatible with this version of Firefox, has version 18, expected 17."
Sorry for that. I'll have to inspect the build process, I will post again when this is fixed.
You're right, it did. (Sorry it took me so long to confirm.)
Build is running, will take 2 to 4 hours. Hope this will fix this issue.
Thanks so much for your help. You guys have been great.
I don't know if I was supposed to test "build date: 2013-01-14 version: 1.6a1pre", but it produced the same incompatible error message and the same symptom as the 01-13 one did.
Please try the version I just uploaded (build date: 2013-01-15), it works for me.
IT WORKS! Ludwig, you are the man. Thank you!
And the original problem is fixed as well?
Yup, all seems great with this 1-15 nightly!