Compatibility between S/MIME v2 & v3 signatures

Gwangsoo Rhee <rhee@sookmyung.ac.kr> Tue, 04 June 2002 01:33 UTC

Received: from above.proper.com (mail.proper.com [208.184.76.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05566 for <smime-archive@lists.ietf.org>; Mon, 3 Jun 2002 21:33:57 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g541Beh22789 for ietf-smime-bks; Mon, 3 Jun 2002 18:11:40 -0700 (PDT)
Received: from sookmyung.ac.kr ([203.252.201.133]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g541Bag22774 for <ietf-smime@imc.org>; Mon, 3 Jun 2002 18:11:36 -0700 (PDT)
Received: from sookmyung.ac.kr (pc-rhee.sookmyung.ac.kr [203.252.195.65]) by cc.sookmyung.ac.kr (8.9.3/8.9.3) with ESMTP id KAA13256 for <ietf-smime@imc.org>; Tue, 4 Jun 2002 10:05:19 +0900 (KST)
Message-ID: <3CFC1315.F8FEA7A8@sookmyung.ac.kr>
Date: Tue, 04 Jun 2002 10:08:37 +0900
From: Gwangsoo Rhee <rhee@sookmyung.ac.kr>
Reply-To: rhee@sookmyung.ac.kr
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf-smime@imc.org
Subject: Compatibility between S/MIME v2 & v3 signatures
Content-Type: text/plain; charset="EUC-KR"
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

Hello, everybody.

Many documents including draft-ietf-smime-rfc2630bis-08.txt
claim that S/MIME v2 & v3 signatures are compatible, BUT:

Sec. 9.4 of RFC 2315 (PKCS #7 v1.5) states about the signature
generation:

   The result of the
   digest-encryption process is the encryption with the signer's private

   key of the BER encoding of a value of type DigestInfo:

   DigestInfo ::= SEQUENCE {
     digestAlgorithm DigestAlgorithmIdentifier,
     digest Digest }

And sec. 5.5 of RFC 2630 (CMS) states:

   The input to the signature generation process includes the result of
   the message digest calculation process and the signer's private key.

This RFC has no mention of DigestInfo structure.
It seems to me that DigestAlgorithmIdentifier doesn't
contribute to the signature generation, and in that case
those two signatures cannot be compatible.

Can anyone please point out where I got this wrong?

Thanks.

--

---------------------------------------
Gwangsoo Rhee <rhee@sookmyung.ac.kr>
tel: +82-2-710-9429  fax: 710-9296
HP: 011-9691-9541
---------------------------------------