RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

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.

Status: Reported (1)

RFC 5754, "Using SHA2 Algorithms with Cryptographic Message Syntax", January 2010

Source of RFC: smime (sec)

Errata ID: 4846
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Annie Yousar
Date Reported: 2016-10-28

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.

Report New Errata