Re: RFC 2634 Questions

suchet singh khalsa <suchetsinghkhalsa@yahoo.com> Mon, 01 September 2003 08:05 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01551 for <smime-archive@lists.ietf.org>; Mon, 1 Sep 2003 04:05:58 -0400 (EDT)
Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h817NDgc057825 for <ietf-smime-bks@above.proper.com>; Mon, 1 Sep 2003 00:23:13 -0700 (PDT) (envelope-from owner-ietf-smime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h817ND19057824 for ietf-smime-bks; Mon, 1 Sep 2003 00:23:13 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-smime@mail.imc.org using -f
Received: from web11807.mail.yahoo.com (web11807.mail.yahoo.com [216.136.172.161]) by above.proper.com (8.12.9/8.12.8) with SMTP id h817NCgc057813 for <ietf-smime@imc.org>; Mon, 1 Sep 2003 00:23:12 -0700 (PDT) (envelope-from suchetsinghkhalsa@yahoo.com)
Message-ID: <20030901072312.51857.qmail@web11807.mail.yahoo.com>
Received: from [148.87.1.171] by web11807.mail.yahoo.com via HTTP; Mon, 01 Sep 2003 00:23:12 PDT
Date: Mon, 01 Sep 2003 00:23:12 -0700
From: suchet singh khalsa <suchetsinghkhalsa@yahoo.com>
Subject: Re: RFC 2634 Questions
To: phoffman@imc.org
Cc: ietf-smime@imc.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>

Hi,
   Resending due to no response. Can anybody please
help me with these questions...

Thanks in advance,
Suchet


--- suchet singh khalsa <suchetsinghkhalsa@yahoo.com>
wrote:
> Hi Paul,
>   Can you please answer the following questions
> w.r.t
> MLA processing of S/MIME messages :
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> According to RFC 2632, while verifying signatures it
> should confirmed that the sender (RFC822 From or
> Sender headers) of the message is the same as the
> signed entity. Does this apply to ONLY the innermost
> signature in a triple wrapped message ?
> If no, this will impact MLA processing as documented
> in RFC 2634 in the following manner :
> 
> 1.  The MLA creates an outermost SignedData layer
> using the private key of the list. The final
> recipient
> will not be able to verify this signature since the
> From header is not the list email address. Is the
> solution here to set the list email address as the
> RFC
> 822 Sender header ?
> 
> 2.  Most MLA's support mail merge functionality. Is
> the intent of RFC 2634 to mandate that S/MIME and
> mail
> merge do not go hand in hand ? The reason for this
> question is : When MLA does mail merge, the
> innermost
> signature in a triple wrapped message will become
> invalid -  so the MLA will have to sign with the
> private key of the list. So, the end recipient will
> not be able to verify this signature since the From
> header of the mail is not the list email address.
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> RFC 2634 does not talk about this case :
> An application/pkcs7-mime bodypart is enclosed in
> another multipart, so that it is not the level 1
> bodypart. What should the MLA do in this case ?
> Possibilities are :
> 1.  Create the outermost signature (according to
> RFC2634 page 34) for the whole mail.
> 
> 2.  Create the outermost signature (according to
> RFC2634 page 34) only for the application/pkcs7-mime
> content.
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> Thanks,
> Suchet
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site
> design software
> http://sitebuilder.yahoo.com
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com