headers
user | 1 Jun 15:57

Signing Messages

Enigmail will not verify a signed email.  It decrypt okay but gives an 
error on just a signed messages.  Checking the same emails with Winpt 
shows good sigs so the messages would appear to formated okay (they are 
signed using the Enigmail add-on).

Actually I never had this issue before 0.95.6, I know previous build 
worked okay but it has been awhile since I had a signed message.

??

Thanks
Permalink | Reply | 2 comments |
headers
Daniel | 2 Jun 03:34
Picon
Favicon

Re: my signature does not verify!


John W. Moore III schrieb:
> 1st....  Is this 'Bug' an "Operator Assisted Failure" or an actual
> failure of Enigmail?  Have You Set the proper Line/Word wrap within
> Thunderbird under 'Account Settings' to 70 or 72 so that the Text
> presented to gpg.exe is 'suitable'?

Sorry for not answering this long time, I didn't relaize that I got answers, got no mail.

I think your tip setting the Word wrap back to 70 fixed it. I set it to 300 earlier beacuse I didn't know that gpg
depends on 70.
Is there any reason why this is fixed to 70, can I increase this setting somewhere?
Permalink | Reply | 5 comments |
headers
Daniel | 2 Jun 03:38
Picon
Favicon

Re: my signature does not verify!


the last mail was send with 300 chars word wrap, this mail with 70.
Why are now both has valid signatures? I dont understand it.

I still have to do some more tests, to check when it will fail again.
Permalink | Reply | 2 comments |
headers
Jean-David Beyer | 1 Jun 21:16
Picon

Re: Signing Messages


user <at> domain.invalid wrote:
> Enigmail will not verify a signed email.  It decrypt okay but gives an 
> error on just a signed messages.  Checking the same emails with Winpt 
> shows good sigs so the messages would appear to formated okay (they are 
> signed using the Enigmail add-on).
> 
> Actually I never had this issue before 0.95.6, I know previous build 
> worked okay but it has been awhile since I had a signed message.
> 
I am currently running version 1.5.0.9 Thunderbird and Enigmail version
0.94.4.0 that are, I believe, the latest for my distro RHEL 5.2. So this
probably does not matter to you, but I will sign this message it that helps.

--
  .~.  Jean-David Beyer          Registered Linux User 85642.
  /V\  PGP-Key: 9A2FC99A         Registered Machine   241939.
 /( )\ Shrewsbury, New Jersey    http://counter.li.org
 ^^-^^ 15:10:01 up 10 days, 5:07, 4 users, load average: 4.37, 4.31, 4.22
Permalink | Reply | 0 comments |
headers
Olav Seyfarth | 1 Jun 23:03
X-Face

Re: Signing Messages


Hi user <at> domain.invalid (!?),

> Enigmail will not verify a signed email.  It decrypt okay but gives an 
> error on just a signed messages.  Checking the same emails with Winpt 
> shows good sigs so the messages would appear to formated okay (they are 
> signed using the Enigmail add-on).

What error?

> Actually I never had this issue before 0.95.6, I know previous build 
> worked okay but it has been awhile since I had a signed message.

Olav
Permalink | Reply | 0 comments |
headers
Faramir | 2 Jun 04:41
Picon

Re: my signature does not verify!


Daniel escribió:
> John W. Moore III schrieb:
>> 1st....  Is this 'Bug' an "Operator Assisted Failure" or an actual
>> failure of Enigmail?  Have You Set the proper Line/Word wrap within
>> Thunderbird under 'Account Settings' to 70 or 72 so that the Text
>> presented to gpg.exe is 'suitable'?
> 
> Sorry for not answering this long time, I didn't relaize that I got answers, got no mail.
> 
> I think your tip setting the Word wrap back to 70 fixed it. I set it to 300 earlier beacuse I didn't know that
gpg depends on 70.
> Is there any reason why this is fixed to 70, can I increase this setting somewhere?

  I don't know, but since the signature block is 64 characters width,
probably there is some relation between both things... And about using
300, I don't know what resolution are you using, but with 1024x768, 300
seems a bit too much...
  Or maybe I am just misunderstanding the whole thing...
Permalink | Reply | 0 comments |
headers
Robert J. Hansen | 2 Jun 04:32
Favicon
Gravatar

Re: my signature does not verify!


Daniel wrote:
> I still have to do some more tests, to check when it will fail again.

Also, please upgrade GnuPG to version 1.4.9.  A security bug was
introduced in the 1.4.8 release.
Permalink | Reply | 0 comments |
headers
John W. Moore III | 2 Jun 05:22

Re: my signature does not verify!


Daniel wrote:
> the last mail was send with 300 chars word wrap, this mail with 70.
> Why are now both has valid signatures? I dont understand it.
> 
> I still have to do some more tests, to check when it will fail again.

One major difference is that without the line wraps 'set' by having the
Setting at 70 or 72 then when hitting Reply Your message is reduced to 1
or 2 loooong lines that run off the edge of the screen forever.  :-\

The Main Reason is that GPG 'looks' for concise blocks of text when
Encrypting Inline.  Word Wrap isn't important when sending with PGP/MIME
but many Mail Clients cannot handle/Open PGP/MIME.  Notably, Outlook,
Outlook Express and Windows Mail. [Windows Mail replaced OE in Vista]

JOHN ;)
Timestamp: Sunday 01 Jun 2008, 23:22  --400 (Eastern Daylight Time)
Permalink | Reply | 0 comments |
headers
Robert J. Hansen | 2 Jun 04:31
Favicon
Gravatar

Re: my signature does not verify!


Daniel wrote:
> I think your tip setting the Word wrap back to 70 fixed it. I set it
> to 300 earlier beacuse I didn't know that gpg depends on 70. Is there
> any reason why this is fixed to 70, can I increase this setting
> somewhere?

This is neither a GnuPG, an Enigmail, nor a Thunderbird bug.

GnuPG detects when a message has been altered.  If you sign a message
with 300-character-long lines, GnuPG will correctly tell you whether the
message is later altered.  If you then have your message pass through an
MTA/MUA that silently breaks your message up into 76-character lines,
well, GnuPG on the other end will detect that the message has been
altered and will tell you so.

No part of the system has failed.  GnuPG has done exactly what it
promised to do and detect modifications.  The MUA has done exactly what
it promised to do and modified the message.

These are called "seam issues" because these are the sorts of problems
that arise at the point where one system ends and another begins, and
neither system is aware of or especially designed to work with the
other.  At the seam between the two parts of the system, problems occur.

Seam issues are also what cause us to strongly advocate turning off
format-flowed messages (often mocked here as "format-flawed", since it
causes more trouble than it's worth).  Your message was sent using
format-flowed.  You may want to look into changing that.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Faramir | 2 Jun 11:10
Picon

Re: Just another person testing enigmail.


Chris De Young escribió:
> Thomas Wootten wrote:
...
>> In particular, how to go about finding out if someone has a key; is
>> there any easy way other than just asking them?
...
> As far as finding out whether someone has a key, you can search the
> popular key servers (I usually use subkeys.pgp.net), or you can ask them
> for it.  Asking them is probably better, if you have a way to be sure
> you know who you're asking, because that way you can make sure that the
> "John Smith" whose key you found is the same John Smith you want to talk
> to.

  I was told pool.sks-keyservers.net is a very good option to upload
(and to search) public keys, since it is a pool of servers, so it is
unlikely it can fail...

 Regards
Permalink | Reply | 0 comments |

Gmane