From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] sup/gpg
Date: Sat, 06 Jun 2009 15:06:49 -0400 [thread overview]
Message-ID: <1244314983-sup-482@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1244314253-sup-6338@cabinet>
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090606/ff5e9ca6/attachment.bin>
next parent reply other threads:[~2009-06-06 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1243463452-sup-1174@cabinet>
[not found] ` <1243466444-sup-3672@ntdws12.chass.utoronto.ca>
[not found] ` <1243622801-sup-6484@cabinet>
[not found] ` <1243819025-sup-136@ntdws12.chass.utoronto.ca>
[not found] ` <1244037417-sup-8346@cabinet>
[not found] ` <1244313900-sup-578@ntdws12.chass.utoronto.ca>
[not found] ` <1244314253-sup-6338@cabinet>
2009-06-06 19:06 ` Ben Walton [this message]
2009-06-08 17:23 ` William Morgan
[not found] ` <1244483397-sup-3035@cabinet>
2009-06-08 18:25 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1244314983-sup-482@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox