[Enigmail] Enigmail bug or failure in my system?

[Charly Avital]

Patrick Brunschwig wrote the following on 5/7/08 2:28 AM:
> Charly Avital wrote:
>> Hi,
> 
>> I am experiencing the following problem, when trying to process (verify)
>> signed messages posted by certain forum members.
> 
>> This same problem existed when I was running Enigmail 0.95.6, and now
>> when I am running Enigmail version 0.96a (20080501).
> 
>> I am running Thunderbird version 2.0.0.14 (20080421) Macintosh, on a
>> Macbook (Intel Processor), with gpg 1.4.9 or gpg2 2.0.9, see details below.
> 
>> *Nothing* happens, the signed message is not processed, there is no
>> output of any kind.
> 
>> I have tried two possible situations:
>> - when 'Automatically Decrypt/Verify Messages' is enabled.
>> - when the above option is not enabled, and I click the 'Decrypt' icon.
> 
>> These messages have in common the following components:
> 
>> - their raw source displays: Content-type: text/plain; charset=utf-8
>> Content-transfer-encoding: base64
>> - instead of the "usual" signed message with PGP headers and footers,
>> the raw source displays a block of rows that contain, each, 76 (seventy
>> six) characters. I would have expected 64 characters, as in base64 format.
> 
> Interesting, I have never seen that. Could you send me such a message?

Hi Patrick,

Thank you for the feedback.

Those messages can be found in Enigmail's list postings. I am afraid
that if I just "fwd" them to you, you will not get the original content.
Here is one example (there are few others); please try to verify it,
and/or to view its raw source. If you do not experience the same problem
as I do, or if you experience different problems, that may be a start to
"assign" the cause/origin of the problem.

Sender                    Subject                                 Date
olav at mozilla-enigmail.org Re: [Enigmail] test encryption features 5/6/08

Copy/paste of the message text:

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

Hi Preeta,

> > I am following the Enigmail Quickstart Guide.

Thank you. That is exactly what you should have done.

Sidenote to other list members: there will be a robot to perform this kind
of task in the future. However, it will still take some time since its
author
is currently busy. But things ar on their way.

> > Could someone test this email for enigmail's encryption features please?

Your message yields the following OpenPGP Security Info:

  Error - signature verification failed

OK, so it did NOT work.

  gpg: Unterschrift vom 05/05/08 23:47:58 mittels DSA-Schlüssel ID AE1D0133

Enigmail works since it found the signature. From the keyID (which is
part of
the signature) it knows which public key to use to decrypt the
signature. But
that key is not yet in the keyring. Since I configured GnuPG (and
Enigmail) to
automatically fetch missing keys (caution, that might bloat your
keyring), gpg
now tries to download and import that key:

  gpg: fordere Schlüssel AE1D0133 von hkp-Server wwwkeys.de.pgp.net an
  gpg: Schlüssel AE1D0133: ֖ffentlicher Schlüssel "preeta
<westr1000 at yahoo.com>"
       importiert
  gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
  gpg:                              importiert: 1

OK, gpg successfully downloaded and imported your public key. Using that key
gpg now decrypts the signature and compares the hash with the
self-calculated
one:

  gpg: FALSCHE Unterschrift von "preeta <westr1000 at yahoo.com>"

They don't match. So the last line indicates a "INCORRECT signature". What
might have caused this? From the layout of your message I suspect line
wrapping.

So I saved your message to a file, removed the line breaks within the
text part
("My name ... please?") and verified using gpg CLI: now it verifies CORRECT.

=> Your Thunderbird and/or Yahoo setup seems to wrap lines where it
should not.

I don't use Yahoo, so I can't tell for sure but I am sure there are
preferences
(Web interface, TB AddOn) concerning whether and when to wrap. Please
set all of
them to e.g. 72 chars and you should be fine. BTW, you can verify that your
settings work by sending to yourself prior to sending to the list.

This all was about signing. You also asked to test encryption. You may send
encrypted message(s) to me to test, but be sure to solve the wrap / signing
issue FIRST.

Olav
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard
Comment: Weitere Informationen:
http://privat.seyfarth.de/olav/schluessel.html

iEYEAREIAAYFAkgf/UsACgkQL/NBt8fdKe2M+wCeMdhB+DF2K5H+3PGQP4CNwOoX
h3QAoLmm7GFa0nCbSouGCBTsGAnwzEAF
=DwtM
-----END PGP SIGNATURE-----
_______________________________________________




TIA,
Charly
MacOS 10.5.2 - MacBook Intel C2Duo - GnuPG 1.4.9 - GPG2 2.0.9 -
Thunderbird 2.0.0.14 - Enigmail 0.96a