errata logo graphic

Found 2 records.

Status: Verified (1)

RFC5754, "Using SHA2 Algorithms with Cryptographic Message Syntax", January 2010

Source of RFC: smime (sec)

Errata ID: 2693

Status: Verified
Type: Editorial

Reported By: Sean Turner
Date Reported: 2011-01-28
Verifier Name: Tim Polk
Date Verified: 2011-03-09

Section 3.3 says:

... the object identifier ecdsa-with-SHA1* (where * is 224, 256, 384, or 512) with absent parameters.

It should say:

... the object identifier ecdsa-with-SHA* (where * is 224, 256, 384, or 512) with absent parameters.

Notes:

r/ecdsa-withSHA1*/ecdsa-with-SHA*
The "1" shouldn't be there the algorithm names are ecdsa-with-SHA224, etc. not ecdsa-with-SHA1224.


Status: Held for Document Update (1)

RFC5754, "Using SHA2 Algorithms with Cryptographic Message Syntax", January 2010

Source of RFC: smime (sec)

Errata ID: 2025

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2010-01-27
Held for Document Update by: Tim Polk
Date Held: 2010-03-21

Section 2.4, pg. 6 says:

2.4.  SHA-512

   [...]

|  The SMIMECapabilities attribute value indicates support for SHA-384
   in a SEQUENCE with the capabilityID field containing the object
|  identifier id-sha384 with absent parameters.  The DER encoding for
   this SMIMECapability value is:

      id-sha512: 30 0b 06 09 60 86 48 01 65 03 04 02 03

It should say:

2.4.  SHA-512

   [...]

|  The SMIMECapabilities attribute value indicates support for SHA-512
   in a SEQUENCE with the capabilityID field containing the object
|  identifier id-sha512 with absent parameters.  The DER encoding for
   this SMIMECapability value is:

      id-sha512: 30 0b 06 09 60 86 48 01 65 03 04 02 03

Notes:

Rationale: Undetected copy&paste error, but significant
(therefore classified as Technical)


Report New Errata