Re: Compatibility between S/MIME v2 & v3 signatures
"Housley, Russ" <rhousley@rsasecurity.com> Tue, 04 June 2002 12:48 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 IAA26088 for <smime-archive@odin.ietf.org>; Tue, 4 Jun 2002 08:48:16 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id g54CZ3j12851 for ietf-smime-bks; Tue, 4 Jun 2002 05:35:03 -0700 (PDT)
Received: from vulcan.rsasecurity.com (mail.rsasecurity.com [204.167.114.123]) by above.proper.com (8.11.6/8.11.3) with SMTP id g54CZ1g12847 for <ietf-smime@imc.org>; Tue, 4 Jun 2002 05:35:01 -0700 (PDT)
Received: from no.name.available by vulcan.rsasecurity.com via smtpd (for mail.imc.org [208.184.76.43]) with SMTP; 4 Jun 2002 12:32:59 UT
Received: from ebola.securitydynamics.com (ebola.securid.com [192.80.211.4]) by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id IAA12807 for <ietf-smime@imc.org>; Tue, 4 Jun 2002 08:35:01 -0400 (EDT)
Received: from exna00.securitydynamics.com (localhost [127.0.0.1]) by ebola.securitydynamics.com (8.10.2+Sun/8.10.2) with ESMTP id g54CX5v25148 for <ietf-smime@imc.org>; Tue, 4 Jun 2002 08:33:06 -0400 (EDT)
Received: by exna00.securitydynamics.com with Internet Mail Service (5.5.2653.19) id <MHPF6ZGH>; Tue, 4 Jun 2002 08:34:59 -0400
Received: from HOUSLEY-LAP.rsasecurity.com (HOUSLEY-LAP [10.3.9.13]) by exna00.securitydynamics.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id MHPF6ZGC; Tue, 4 Jun 2002 08:34:52 -0400
From: "Housley, Russ" <rhousley@rsasecurity.com>
To: rhee@sookmyung.ac.kr
Cc: ietf-smime@imc.org
Message-Id: <5.1.0.14.2.20020604082808.03627df8@exna07.securitydynamics.com>
X-Sender: rhousley@exna07.securitydynamics.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 04 Jun 2002 08:30:43 -0400
Subject: Re: Compatibility between S/MIME v2 & v3 signatures
In-Reply-To: <3CFC1315.F8FEA7A8@sookmyung.ac.kr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
Gwangsoo: RFC 2315 only supports PKCS#1 v1.5 RSA signatures. RFC 2630 and rfc2630bis support any signature algorithm. So, the more correct backward compatibility statement is: RFC 2630 is backwards compatible with RFC 2315 when PKCS#1 v1.5 RSA signatures are used. Russ At 10:08 AM 6/4/2002 +0900, Gwangsoo Rhee wrote: >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 >---------------------------------------
- Compatibility between S/MIME v2 & v3 signatures Gwangsoo Rhee
- Re: Compatibility between S/MIME v2 & v3 signatur… Housley, Russ
- Re: Compatibility between S/MIME v2 & v3 signatur… Gwangsoo Rhee
- Re: Compatibility between S/MIME v2 & v3 signatur… Housley, Russ