Excerpts from William Morgan's message of Mon Jun 08 13:23:43 -0400 2009: > Reformatted excerpts from Ben Walton's message of 2009-06-06: > What was the patch?
The regexp fix for messages with very long lines. > Yeah, an incorrect passphrase will error out, it won't produce a bad > message. Yeah, it bounces me back to pinentry, where I proceeded to enter it correctly. It *shouldn't* produce a bad message, it was just one of the only things I could think of that had changed between the two messages which might have led to different behavior. > That is where I would start looking. If you tweak crypto.rb so that it > dumps the payload somewhere (look in #format_payload), you can then > compare that to what ends up in your sent.mbox. I'll take a look at this... > Also you can look at encrypting messages to yourself. Are you able to > decrypt them reliably? If not, is there a pattern? (Non-ASCII in the > headers, body, etc.?) I expect this will have the same behavior as checking signatures on messages I send, no? Just a little background that we discussed before forwarding this to the list: Ben is using gpg 1 after correspondents complained the switch to gpg 2 caused his messages to have bad signatures. I am using gpg 2.0.11 I see *all* Ben's messages as having bad signatures, and see all my own (either in sent.mbox or bounced back to me from the list) as good. I also see Ben's signatures as bad when looking at the same messages through mutt. I see the same thing going back to his first signed message to sup-talk, and also in his direct emails to me. Ben sees most of my signatures as good, but has recently experienced an intermittent issue where my signatures are bad.
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
