[Enigmail] Enigmail bug or failure in my system?

Wed May 7 02:09:48 PDT 2008

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Olav Seyfarth wrote:
> Hi Charly,

Hi Olav,

I am now in Linux Ubuntu 8.04.

signature verifies, your picture is there, and the raw source displays:
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

> Patrick, this is Charly's debug output:
> 
>   enigmail> /usr/local/bin/gpg2 --charset utf8 --batch --no-tty --status-fd 2
>       --keyserver-options auto-key-retrieve --keyserver keyserver.linux.it -d
>   gpg: Signature made Tue May  6 02:40:11 2008 EDT using DSA key ID C7DD29ED
>   gpg: BAD signature from "Olav Seyfarth (privat) <olav at seyfarth.de>"
>   enigmail.js: Enigmail.decryptMessageEnd: Error in command execution
> 
> So he is using gpg2 - but I don't understand the -d in the command line since
> this message was not encrypted but to be verified.

I can use gpg2 2.0.9 or gpg 1.4.9, by changing OpenPGP Preferences. Can
this be a cause to the problem I am experiencing?

I want to stress once more, and sorry for being a bore, that the problem
   I have described: signed message is not processed, no warning or
error message, just nothing, and it relates *only* to messages that show
content type: charset utf-8 and content-transfer encoding base64.
> 
> Since these problems only occured approximately after the release of Thunderbird
> 2.0.0.14, might it be possible that it is a regression from TB (CR/FL issues)?

I wouldn't know. All other signed messages (except for what I have
already indicated) are processed correctly. Most of the time the
signature verifies, sometimes it is bad, but there is a result.
> 
> Charly, to debug, please move aside your program and profile directories and
> install just a TB 2.0.0.14 + EM 0.95.6 (release version). If it yields the same
> error, please try with TB 2.0.0.13 + EM 0.95.6 (release version).

I'll do that in MacOSX. Both MacOSX and Linux are running side by side,
and are a keyboard shortcut away, no need to reboot.

But now I have to leave home and computer for a couple of hours, to
fulfill some obligations in the real world :-).

I shall back at you as soon as I have carried out the actions you describe.
> 
> Maybe specialities about my key / GnuPG / DSA2 settings? Hmmm, see yourself:
> 
>   > list
> 
>   pub  1024D/C7DD29ED  erzeugt: 2004-11-13  verfällt: 2009-12-31  Aufruf: SC
>                        Vertrauen: uneingeschränkt Gültigkeit: uneingeschränkt
>   sub  2048g/642183AD  erzeugt: 2004-11-13  verfällt: 2009-12-31  Aufruf: E
>   [ uneing.] (1). Olav Seyfarth (privat) <olav at seyfarth.de>
>   [ uneing.] (2)  [jpeg image of size 3458]
>   [ uneing.] (3)  Olav Seyfarth (Enigmail) <olav at mozilla-enigmail.org>
> 
>   > showpref
> 
>   [ uneing.] (1). Olav Seyfarth (privat) <olav at seyfarth.de>
>        Verschlü.: AES256, AES192, AES, CAST5, 3DES
>        Digest: SHA1, SHA256, RIPEMD160
>        Komprimierung: ZLIB, BZIP2, ZIP, nicht komprimiert
>        Eigenschaften: MDC, Keyserver no-modify
>   [ uneing.] (2)  [jpeg image of size 3458]
>        Verschlü.: AES256, AES192, AES, CAST5, 3DES
>        Digest: SHA1, SHA256, RIPEMD160
>        Komprimierung: ZLIB, BZIP2, ZIP, nicht komprimiert
>        Eigenschaften: MDC, Keyserver no-modify
>   [ uneing.] (3)  Olav Seyfarth (Enigmail) <olav at mozilla-enigmail.org>
>        Verschlü.: AES256, AES192, AES, CAST5, 3DES
>        Digest: SHA1, SHA256, RIPEMD160
>        Komprimierung: ZLIB, BZIP2, ZIP, nicht komprimiert
>        Eigenschaften: MDC, Keyserver no-modify
> 
>   gpg.conf:
> 
>   no-greeting
>   enable-dsa2
>   default-key 0x2FF341B7C7DD29ED
>   encrypt-to 0x2FF341B7C7DD29ED
>   personal-digest-preferences SHA256 SHA512 SHA1 RIPEMD160 SHA224 SHA384 MD5
>   keyserver-options include-subkeys
>   ask-cert-level
>   import-options repair-pks-subkey-bug import-clean
>   export-options export-clean
>   keyserver x-hkp://pgpkeys.pca.dfn.de
> 
> I used SHA256 to sign the message in question.
> 
> Olav
> /tmp/gpg-ABAdXF/2FF341B7C7DD29ED.jpg is a 90x120 JPEG image, color space YCbCr, 3 comps, Huffman coding.
>   Using TrueColor visual
>   Building XImage...done

I am far from being an expert, but I can't find anything unusual in your
key "specialties" nor in your gpg.conf. Ninety-nine-comma-ninety-nine
percent of your signed messages verify without the least problem. It's
only that utf-8 base64 that fails to be processed. Similar messages
(utf-8 and base64) from two other forum members fail also.

As a matter of fact the message posted by you, that fails, quotes one of
the other messages that fail to be processed. Therefore it is possible
that there is nothing "wrong" with your key and gpg.conf, and that the
issue is with those two forum members who are posting messages with
utf-8 *and* base64.

I am back as soon as possible.
Charly
Ubuntu 8.04 (under virtual ware) - GnuPG 1.4.9 - gpg2 2.0.9 -
version 2.0.0.14 (20080505) - Enigmail 0.96a

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJIIXHXAAoJEM3GMi2FW4Pvbd0H/Rby9VkxIwp+8CihgmjAY0St
aQE0fMx/IRBlBTr17MMMjw+1+mi99QRQv/1x+NcLvpXUG7zXVeNeKQ6bKw9iQHNx
uRDUox/ZyhONj/EkTWpg+0LjJqNaxjSuvJPyEIp88hydnjgEICD9YczjGuaRr3vu
4+Qp9qBPaNamQWsE6z5HsuaRwsc4L6e1ULGxoKs3d/pABgCwVxVap5JfisW29vXg
F3aAO2UOhdgkTDTcIjXMF08xO6hcgFyCSsdaVLHR8eGLQwyxbxFnF+NGB2AI5BCv
PAy8+FP+vKz8rirnlCcJ7VGEbHnc8/AqJvwas700g4Ea5lewEa98S6+BZe/SEaw=
=gyPn
-----END PGP SIGNATURE-----