Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: Gnus mishandled PGP clearsigned files in attachments
Date: Mon, 23 Jan 2006 18:53:42 +0900	[thread overview]
Message-ID: <b4mvewbqnh5.fsf@jpl.org> (raw)
In-Reply-To: <b4m1wyzwo5v.fsf@jpl.org>

>>>>> In <b4m1wyzwo5v.fsf@jpl.org> Katsumi Yamaoka wrote:

>>   - when saving such an attachment, Gnus discards the PGP armour (and
>>     therefore the signature).  This makes it impossible to check the
>>     signature.

> We don't have a means to do it up to now, but I'll grope the way
> to achieve it...

I've modified the Gnus trunk (i.e., No Gnus) so as to display
extra buttons that point parts containing PGP signatures.  You
can enable it by typing the M-t key in the summary buffer, or
always display those buttons by setting the
`mm-uu-buttonize-original-text-parts' variable to non-nil.

>> gmane.comp.version-control.darcs.devel under

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

And this article will be displayed as follows:

[2. The original part of --- text/x-darcs-patch; save-email-description-file-if-a-send-fails.dpatch]...

[[PGP Signed Part:Undecided]]
[3. text/x-darcs-patch; save-email-description-file-if-a-send-fails.dpatch]

The part 2 contains a PGP signature, but the part 3 doesn't.  Is
this behavior ok?

P.S. I made a mistake in writing cvs log, sorry.



  reply	other threads:[~2006-01-23  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22 23:04 Juliusz Chroboczek
2006-01-23  4:42 ` Katsumi Yamaoka
2006-01-23  9:53   ` Katsumi Yamaoka [this message]
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=b4mvewbqnh5.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    /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).