Re: block padding formats

Petra:

We discovered that the OIW OID was not used with PKCS#1 padding.  It
referenced another padding scheme.  We founf that RSA Labs had assigned an
OID that used PKCS#1 padding, the technique that we intended alll along.

Russ


At 11:46 AM 8/18/98 +0200, Petra Glöckner wrote:
>Hello,
>
>reading draft-ietf-pkix-ipki-part1-07 and draft-ietf-pkix-ipki-part1-09 
>I noticed the following difference:
>
>draft-ietf-pkix-ipki-part1-07 states:
>> The signature algorithm with SHA-1 and the RSA encryption algorithm
>> is defined in by the OSI Interoperability Workshop in [OIW]. Padding
>> conventions described in PKCS #1, section 8.1, must be used.  As
>> defined in [OIW], the ASN.1 object identifier used to identify this
>> signature algorithm is:
>> 
>>         sha1WithRSASignature OBJECT IDENTIFIER  ::=  {
>>             iso(1) identified-organization(3) oiw(14)
>>             secsig(3) algorithm(2) 29  }
>> 
>
>draft-ietf-pkix-ipki-part1-09 states:
>> The signature algorithm with SHA-1 and the RSA encryption algorithm
>> is implemented using the padding and encoding conventions described
>> in PKCS #1 [RFC 2313]. The message digest is computed using the SHA-1
>> hash algorithm.  The ASN.1 object identifier used to identify this
>> signature algorithm is:
>> 
>>         sha-1WithRSAEncryption OBJECT IDENTIFIER  ::=  {
>>             iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
>>             pkcs-1(1) 5  }
>
>
>Why did you replace the OIW ObjId with the RSA ObjId ? Is it because 
>the OIW ObjId 1.3.14.3.2.29 doesn't identify PKCS #1 padding but
>9796-1 padding ? Has the draft-ietf-pkix-ipki-part1-07 been wrong at 
>this point ?
>
>Best regards - Petra Glöckner
>
>