Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: michael+sup@stapelberg.de (Michael Stapelberg)
Subject: [sup-talk] [BUG] [PATCH] Encrypted messages without signature generate an exception
Date: Tue, 29 Sep 2009 20:43:09 +0200	[thread overview]
Message-ID: <1254249719-sup-3652@midna.zekjur.net> (raw)

Hi,

when viewing (or replying to) an encrypted message without a signature,
sup throws an exception because of a nil chunk. I?ve attached a patch
which fixes the issue by instead providing a message stating that this
mail is not signed.

Best regards,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Bugfix-Display-a-notice-when-a-mail-is-not-signed.patch
Type: application/octet-stream
Size: 1212 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090929/1351e062/attachment.obj>


                 reply	other threads:[~2009-09-29 18:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1254249719-sup-3652@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