Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Accepting x-pkcs7-signature
Date: Fri, 23 Jul 2010 20:13:35 +0200	[thread overview]
Message-ID: <877hkmoyls.fsf@randomsample.de> (raw)
In-Reply-To: <87eieu456i.fsf@broken.deisui.org> (Daiki Ueno's message of "Fri, 23 Jul 2010 23:57:09 +0900")

Daiki Ueno writes:
> David Engster <deng@randomsample.de> writes:
>
>>>>  					   ctl 'protocol)
>>>>  					  "application/pkcs7-signature")
>>>
>>> ^^ this line should also be changed to accept "x-pkcs7-signature"?
>>
>> The full sexp is this:
>>
>>  (setq part (mm-find-raw-part-by-type
>> 				  ctl (or (mm-handle-multipart-ctl-parameter
>> 					   ctl 'protocol)
>> 					  "application/pkcs7-signature")
>> 				  t)))
>>
>> So I thought this would just be used as a fallback?
>
> Well, I looked at the following code and thought that PART was
> signed material:
>
> (setq plain (epg-verify-string context (mm-get-part signature) part)

To be honest, I really have problems understanding what all that
'mm'-code does. It seems to me the HANDLE structure already has all the
information that's needed, including pointers to the buffers containing
the text and the detached signature, but somehow it extracts them
again. I also don't understand the above fallback for
"application/pkcs7-signature", since multipart/signed must have a
'protocol' parameter in the Content-Type anyway, otherwise it's just
broken.

Regards,
David



  reply	other threads:[~2010-07-23 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-22 21:11 David Engster
2010-07-23  8:53 ` Daiki Ueno
2010-07-23 10:32   ` David Engster
2010-07-23 14:57     ` Daiki Ueno
2010-07-23 18:13       ` David Engster [this message]
2010-07-24  1:21         ` Daiki Ueno

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=877hkmoyls.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --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).