From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup/gpg
Date: Mon, 08 Jun 2009 10:23:43 -0700 [thread overview]
Message-ID: <1244481592-sup-4821@entry> (raw)
In-Reply-To: <1244314983-sup-482@ntdws12.chass.utoronto.ca>
Reformatted excerpts from Ben Walton's message of 2009-06-06:
> 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:
> > 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.
What was the patch?
> > 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.
Yeah, an incorrect passphrase will error out, it won't produce a bad
message.
> I think that's reasonable. My next thought is that there is a small
> bug in the mime parsing (or creating) code...
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.
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.?)
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-06-08 17:23 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
2009-06-08 17:23 ` William Morgan [this message]
[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=1244481592-sup-4821@entry \
--to=wmorgan-sup@masanjin.net \
/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