Bug#519183: trying to replicate enigmail clearsigned message failure [was: Re: Advocating for Prach Pongpanich]

[Thomas Goirand]

On 05/22/2013 01:53 PM, Daniel Kahn Gillmor wrote:
>> Thanks for this message.
>> I think this must be related to #519183.
>
>
> this bug report suggests there is something going wrong with line
> wrapping. which lines? do you have a way to generate the same problem
> with a simple test message? I've been trying with the packages from
> wheezy and a test 1024-bit DSA key and have not been able to replicate
> the problem.

Yeah, quite annoying that it just doesn't work "some times"...

> I'm wondering if there is some setting that you have configured that is
> different from the default config i'm using to replicate.

No, same setting. I didn't change anything. I don't think that's the
problem.

>> When sending my mail, I noticed that there was an added blank
>> line before the <begin-signed-message> thing.
>
> can you be more specific about what you mean with "the <begin-signed
> message>" thing? i don't see any text with that literal value in my
> testing.

I'm sorry, I meant:

-----BEGIN PGP SIGNED MESSAGE-----

I think what you can try to replicate my problem is just to hit reply on
the message which I was trying to reply to. Eg:
<2013051908...@gmail.com>, then try to send a signed response.

Thomas


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Daniel Kahn Gillmor]

Control: found -1 2:1.4.1-2
Control: found -1 2:1.5.1+id17

On 05/22/2013 03:18 AM, Thomas Goirand wrote:

> No, same setting. I didn't change anything. I don't think that's the
> problem.

is your account configured to "compose messages in HTML format" or not?

> I think what you can try to replicate my problem is just to hit reply on
> the message which I was trying to reply to. Eg:
> <2013051908...@gmail.com>, then try to send a signed response.

ah, interesting. I was doing this without "compose messages in HTML
format" checked, and was unable to replicate the bug.

when composing a reply in HTML format, i managed to hit the bug repeatedly.

So i think the sequence is:

* open a message (for reading) that has at least one long line (longer
than 78 chars)

* reply to it in such a way that you get the HTML composer and not the
plaintext composer

* use inline PGP (do not use PGP/MIME)

* indicate that you want to sign the message, but not encrypt it.

* send the reply.

Sending the reply produces a warning dialog box like the following:

>> HTML mail warning:
>> This message may contain HTML, which could cause signing/encryption to
>> fail. To avoid this in the future, you should press the SHIFT key when
>> clicking on the Compose/Reply button to send signed mail.
>>
>> If you sign mail by default, you should uncheck the 'Compose Messages
>> in HTML' preference box to permanently disable HTML mail for this mail
>> account.
>>
>> This alert will repeat 2 more times.


This appears to be repeatable with a stock wheezy icedove/enigmail
installation with no changes to the default config. It also happens in
1.5.1+id17 (from sid), in my testing just now.

So upstream appears to know about the problem, and recommends explicitly
not using the cluster of configurations that i've outlined above.

zigo, are you running enigmail with the configuration described above?

can you show me the output of the following two commands:

grep enigmail.composeHtmlAlertCount ~/.icedove/*/prefs.js
grep compose_html ~/.icedove/*/prefs.js


Regards,

--dkg

[Thomas Goirand]

On 05/22/2013 09:39 PM, Daniel Kahn Gillmor wrote:
> Control: found -1 2:1.4.1-2
> Control: found -1 2:1.5.1+id17
>
> On 05/22/2013 03:18 AM, Thomas Goirand wrote:
>
>> No, same setting. I didn't change anything. I don't think that's the
>> problem.
>
> is your account configured to "compose messages in HTML format" or not?

Unfortunately, it seems it was, yes. Though I had set the debian.org to
receive plain text, so I believe Icedove was trying to convert to plain
text.

Now that I've seen such option, I've untick it, so it wont bother me
again. That configuration was annoying me for years!!! :)

> This appears to be repeatable with a stock wheezy icedove/enigmail
> installation with no changes to the default config. It also happens in
> 1.5.1+id17 (from sid), in my testing just now.
>
> So upstream appears to know about the problem, and recommends explicitly
> not using the cluster of configurations that i've outlined above.
>
> zigo, are you running enigmail with the configuration described above?
>
> can you show me the output of the following two commands:
>
> grep enigmail.composeHtmlAlertCount ~/.icedove/*/prefs.js
> grep compose_html ~/.icedove/*/prefs.js

Sure!

zigo@GPLHost:buzig>_ ~ # grep enigmail.composeHtmlAlertCount
.icedove/r72qm86t.default/prefs.js
user_pref("extensions.enigmail.composeHtmlAlertCount", 0);
zigo@GPLHost:buzig>_ ~ # grep compose_html
.icedove/r72qm86t.default/prefs.js
user_pref("mail.identity.id1.compose_html", false);
user_pref("mail.identity.id2.compose_html", false);
user_pref("mail.identity.id5.compose_html", false);
user_pref("mail.identity.id6.compose_html", false);