1 Topic by Kevin Cole

  • Kevin Cole
  • Guest

Topic: Gmail word wrap issue.

Hi,

I'm just trying out your extension.  First, it's worth telling people that they need to set their gmail compose to plain-text rather than rich formatting.  At least, I think that's what I needed to do.

Also, it looked like gmail word-wrapped the message AFTER signing it.  That made the signature fail.  Am I interpreting the problem correctly?

Thanks.

2 Reply by Kevin Cole

  • Kevin Cole
  • Guest

Re: Gmail word wrap issue.

P.S. I'm using Kubuntu 6.10 (Edgy).  Also, when sending a signed message from Thunderbird with Enigmail, I had to remember to disable the PGP/MIME so that the signature was in-line, rather than appearing as an attachment.

  • cmdln
  • New member
  • Offline
  • Registered: 2007-04-04
  • Posts: 5

Re: Gmail word wrap issue.

I have the same problem with word wrapping in Gmail.  Not sure how to workaround it, since the Gmail settings don't seem to give any control over wrapping.

Perhaps if FireGPG had an option to hard wrap the selection before signing, then it might not trigger Gmail's wrapping?  Or maybe there is a way to sign that ignores EOL?

Let me know if I can help, I think this is a great extension.

As I mentioned in another post, I am running OS X, 10.4.9.

4 Reply by Brandon

  • Brandon
  • Guest

Re: Gmail word wrap issue.

The signature is failing for me as well.  I am using 0.3.1 and GnuPG on Windows.  It seems that the encryption is working.

  • cmdln
  • New member
  • Offline
  • Registered: 2007-04-04
  • Posts: 5

Re: Gmail word wrap issue.

If I sign some text in Gmail then re-select the signed block and verify, all without sending, it verifies just fine.  I think the word wrap interpretation is accurate.

  • Registered: 2007-04-05
  • Posts: 3

Re: Gmail word wrap issue.

Just had the same Problem. Some links (e.G. the one of firegpg itself at the bottom) were HTMLized and the Plugin reportet it's own signature as invalid.

7 Reply by Aluink

  • Aluink
  • Guest

Re: Gmail word wrap issue.

If you check the signature right after signing it and don't send it it works fine, the word wrapping there doesn't break anything.  The issue comes into play when you send a message.  GMail adds newlines instead of wrapping long lines to messages it sends.  This alters the message and thus causes the signatures to fail.

8 Reply by wnagele

  • wnagele
  • Guest

Re: Gmail word wrap issue.

I guess this is one of the MOST important bugs currently. It's sad that there is no bug tracking to pressure this. As far as i could reproduce it it's not just a problem in the presentation layer - it really sends wrong signatures. But i was not able to reproduce the exact case when this happens - it also looks like kind of "random" to me. But i guess there has to be some kind of trigger. However same mails sometimes fail and sometimes go ok in my case. Hope there will be a fix soon.

If anyone has a hint or an exact problem description that would help a lot.

  • Registered: 2007-04-09
  • Posts: 8

Re: Gmail word wrap issue.

i've noticed that if i take a message that was sent to me and copy the whole thing.  then if i remove the newlines gmail added to wordwrap, the signature passes perfectly.  like i said before, it seems that gmail adds "\n" during transmission when the text wraps.

ie:

Original text:
"Some text here to make lots of space...and then some more and more.  Lalalalala, I"m just making a big long ling"

"Gmail'ed" text:
"Some text here to make lots of space...and
then some more and more.  Lalalalala, I"m
just making a big long ling"

By removing the hard '\n' from the latter text and making it like the former, the signature passes.  Which suggest that FireGPG does fine in signing and verifying, it's just that the text actually gets modified.  And thus, like the signature verification process is supposed to do, it tells you it doesn't pass and was modified wink

10 Reply by ben

  • ben
  • New member
  • Offline
  • Registered: 2007-05-01
  • Posts: 1

Re: Gmail word wrap issue.

I just wanted to confirm this. If you compose in plain text mode, the signature will be formed from the unwrapped version of your message causing subsequent verifcation to fail. "Rich text" mode appears to work, because no wrapping is needed there.

In this example, _sent_ contains what I saw in the message window before sending, and _rec_ contains the body of the same email once received. 

ben@dev:/tmp$ cat sent 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGN0u+VsSLShHy9OARApHnAJoCZ22eAdEQ742SS87/rG7DDOVTggCfQZmP
AVxffs3ekhHLYozyd75ayKM=
=ZNVZ
-----END PGP SIGNATURE-----

ben@dev:/tmp$ cat rec
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: http://firegpg.tuxfamily.org

iD8DBQFGN0u+VsSLShHy9OARApHnAJoCZ22eAdEQ742SS87/rG7DDOVTggCfQZmP
AVxffs3ekhHLYozyd75ayKM=
=ZNVZ
-----END PGP SIGNATURE-----

ben@dev:/tmp$ diff sent rec
4c4,7
< aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
---
> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
  • From: Geneva
  • Registered: 2007-04-04
  • Posts: 1,040

Re: Gmail word wrap issue.

We will see.

the_glu's Website

  • Registered: 2007-05-27
  • Posts: 10

Re: Gmail word wrap issue.

Wrapping should have no affect on verification.  Email of course MUST send with CR+LF.  But if you are on some version of 'Nix that gets translated to just a LF on receipt, or the LF -> CR+LF when sending.  If you are on Windows or OpenVMS that would continue to be CR+LF.  But verification is supposed to toss out both CR and LF characters in doing the signing and verifying.  If you want the WebMail that is the worst in how wrapping of things is done, that has to be Yahoo.  I have done extensive tests of the signing problem and they are available in the following file:

http://www.securemecca.com/FireGPG.zip

In short signing of WebMail messages with FireGPG is a big problem and generally speaking, making yourself GMail-centric is bound to blind you to what is going wrong.  The common format that all Mail User Agents have is plain ASCII text.  Actually, that is all that is sent anyway, and MIME markings will occur for anything that is not in that format.  Further, if youhave only LF in your ASCII text they must be converted to CR+LF before they are sent down the pipeline. I am talking about the actual transport.  It really helps to have POP mail since you can save the message to a file (don't do decryption in the MUA) and you can see all the MIME markings (but the text that was sent is always ASCII with CR+LF line endings with the MIME markings around the various pieces).  With WebMail what you see and what is may be worlds apart.  I tried saving the entire mess in Yahoo, and at the time that confused rather than enlightened me.

What you want though is not just a GMail-centric thing.  You want somebody on the other end to be able to verify a message whether they are using GMail, Yahoo WebMail, HotMail, AOL/Netscape, or a POP or IMAP mail account.  BTW, you can transform your GMail into a POP server if so desired.
If that requires plain text so be it - that is the best choice.