Excerpts from Marc Hartstein's message of Sat Jun 06 14:53:55 -0400 2009:
> Excerpts from Ben Walton's message of Sat Jun 06 14:45:56 -0400 2009:
> > 
> > This just got stranger, which makes me think it may be a sup issue
> > still.  The thread you replied twice to earlier today has one message
> > validating and the other not.  See attached.
> 
> Ok, that's totally bizarre.
> 
> Things I can think of:
> 
> Those were two different sup instances (I'd quit, created a branch, and
> applied the discussed patch in between sending the two replies)

Well, if the patch altered the behaviour, that's a possibility.

> I might well have typoed my passphrase for one of the messages and not
> the other, though I'm not sure which.  I think it's slightly more likely
> that the BAD message was the one where I made a typo, though.  [I then
> proceeded to enter it correctly the second time, though, so...]

When I enter a bad passphrase into pinentry, sup detects this and
won't send the message...to my knowledge, I'm not able to get a
multipart/gpg message sent if I don't enter a proper passphrase.

> Think we should move the discussion to the sup list to see if anybody
> has thoughts?

I think that's reasonable.  My next thought is that there is a small
bug in the mime parsing (or creating) code...

Does anyone else have thoughts on what would cause broken gpg
signatures?  I've previously had issues when using gpg2 instead of
gpg1, but that was completely the fault of gpg2 (or my use of it,
anyway).  Switching to gpg1 resolved the problem at that time.  In
this instance, Mark isn't able to validate my signatures and I was
able to validate his until just recently...I'm now hit-and-miss with
his.

Thoughts?

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.

Attachment: signature.asc
Description: PGP signature

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

Reply via email to