RE: Incorrect OID used in example 6.1

Magnus,

Thank you very much for your feedback.

Jim Schaad created the 6.1 example included in the Examples-05 document.  I
agree with your comment that when using E-S D-H, the KeyAgreeRecipientInfo
keyEncryptionAlgorithm OID must be id-alg-ESDH defined in RFC 2630, Section
12.3.1.1 (1 2 840 113549 1 9 16 3 5).  Recommend that Jim should re-generate
the 6.1 example using the correct KeyAgreeRecipientInfo
keyEncryptionAlgorithm OID (or we could do it, if required).

The same problem exists in the 6.9 example that we created.  We will
re-create the 6.9 example with the E-S D-H KeyAgreeRecipientInfo
keyEncryptionAlgorithm OID set to id-alg-ESDH.

Please note that our new 6.10 example correctly includes the E-S D-H
KeyAgreeRecipientInfo  keyEncryptionAlgorithm OID set to id-alg-ESDH.

Thanks again,
===========================================
John Pawling, [email protected]
Getronics Government Solutions, LLC
===========================================


-----Original Message-----
From: Magnus Svensson [mailto:[email protected]]
Sent: Sunday, February 04, 2001 11:23 AM
To: 'Pawling, John'; [email protected]
Subject: Incorrect OID used in example 6.1


John,

I think I discovered another error in the 6.1 example. The
keyEncryptionAlgorithm in the KeyAgreeRecipientInfo structure is encoded as
follows in the 6.1 example:

SEQUENCE {
  OBJECT IDENTIFIER dhPublicNumber (1 2 840 10046 2 1)
  SEQUENCE {
    OBJECT IDENTIFIER '1 2 840 113549 1 9 16 3 6'
    NULL
  }
}

Since the 6.1 example uses Ephemeral-Static DH the
keyEncryptionAlgorithm-identifier should not be dhPublicNumber as displayed
above. According to CMS (RFC2630) section 12.3.1.1 the
keyEncryptionAlgorithm-identifier should be the id-alg-ESDH (1 2 840 113549
1 9 16 3 6) instead.

Regards,
Magnus