RFC Errata
Found 3 records.
Status: Verified (2)
RFC 5754, "Using SHA2 Algorithms with Cryptographic Message Syntax", January 2010
Source of RFC: smime (sec)
Errata ID: 2693
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
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.
Errata ID: 4846
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Annie Yousar
Date Reported: 2016-10-28
Verifier Name: Roman Danyliw
Date Verified: 2022-01-20
Section section 3.2 says:
The SMIMECapabilities attribute value indicates support for one of | the DSA signature algorithms in a SEQUENCE with the capabilityID field containing the object identifier sha*WithRSAEncryption (where * is 224, 256, 384, or 512) with NULL parameters.
It should say:
The SMIMECapabilities attribute value indicates support for one of | the RSA signature algorithms in a SEQUENCE with the capabilityID field containing the object identifier sha*WithRSAEncryption (where * is 224, 256, 384, or 512) with NULL parameters.
Notes:
The section 3.2 is related to RSA.
Status: Held for Document Update (1)
RFC 5754, "Using SHA2 Algorithms with Cryptographic Message Syntax", January 2010
Source of RFC: smime (sec)
Errata ID: 2025
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
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)