From: michael+sup@stapelberg.de (Michael Stapelberg)
Subject: [sup-talk] Bug: Messages using inline GPG are not decrypted
Date: Sat, 26 Sep 2009 23:41:58 +0200 [thread overview]
Message-ID: <1254001238-sup-5754@midna.zekjur.net> (raw)
In-Reply-To: <1253996823-sup-6670@midna.zekjur.net>
Hi,
Excerpts from Michael Stapelberg's message of Sa Sep 26 22:28:54 +0200 2009:
> The changes basically work. The message itself is opened and decrypted
> correctly. However, when handling some messages, an exception occurs
> (downcase called on NilClass), which can be fixed like this:
I noticed that this is not the only place where this was wrong. Complete
patch attached (also fixes mixups like control.header.downcase.content_type
vs. control.header.content_type.downcase).
Best regards,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-downcase.patch
Type: application/octet-stream
Size: 2375 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090926/da544580/attachment.obj>
next prev parent reply other threads:[~2009-09-26 21:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 17:05 Michael Stapelberg
2009-09-22 17:24 ` Michael Stapelberg
2009-09-25 19:10 ` Michael Stapelberg
2009-09-26 18:09 ` William Morgan
2009-09-26 20:28 ` Michael Stapelberg
2009-09-26 21:37 ` Ben Walton
2009-09-26 21:41 ` Michael Stapelberg [this message]
2009-09-27 1:40 ` 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=1254001238-sup-5754@midna.zekjur.net \
--to=michael+sup@stapelberg.de \
/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