Gnus development mailing list
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.jussieu.fr>
Subject: Gnus mishandled PGP clearsigned files in attachments
Date: Mon, 23 Jan 2006 00:04:47 +0100	[thread overview]
Message-ID: <7ifynf984w.fsf@lanthane.pps.jussieu.fr> (raw)

Hi,

(I've also reported this as Debian bug 348383 -- sorry for the spamming.)

Gnus mishandles ASCII-armored GPG signed files sent as attachments.
An example of such a file is available on gmane in group
gmane.comp.version-control.darcs.devel under

  Message-ID: <200601142043.k0EKhTvU018182@ms-smtp-02.nyroc.rr.com>

There are two mis-behaviours:

  - when displaying such a message, Gnus will attempt to verify the
    signature before de-QP-ing.  Obviously, this fails;
  - when saving such an attachment, Gnus discards the PGP armour (and
    therefore the signature).  This makes it impossible to check the
    signature.

Mutt simply treats the attachment as plain text:

  - when displaying such a message, Mutt doesn't attempt to do any
    processing.
  - when saving such an attachment, Mutt saves the pristine, de-QP-ed
    attachment, which it is then possible to verify.

Ideally, Gnus would behave like Mutt when saving the attachment, but
verify the signature after de-QP-ing when displaying the message.

(In case you're interested: there are very good reasons for using this
sort of attachments -- the attachment can be verified after being
saved without using a mailer, which is not the case with PGP/MIME.
This is a needed feature in Darcs.)

Thanks for your help,

                                        Juliusz Chroboczek




             reply	other threads:[~2006-01-22 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22 23:04 Juliusz Chroboczek [this message]
2006-01-23  4:42 ` Katsumi Yamaoka
2006-01-23  9:53   ` Katsumi Yamaoka
2006-01-23 11:55     ` Katsumi Yamaoka
2006-01-24 10:28       ` Katsumi Yamaoka
2006-01-24 20:39         ` Juliusz Chroboczek

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=7ifynf984w.fsf@lanthane.pps.jussieu.fr \
    --to=jch@pps.jussieu.fr \
    /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;
as well as URLs for NNTP newsgroup(s).