RFC Errata
RFC 4634, "US Secure Hash Algorithms (SHA and HMAC-SHA)", July 2006
Note: This RFC has been obsoleted by RFC 6234
Source of RFC: IETF - NON WORKING GROUPArea Assignment: sec
Errata ID: 2437
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-08-13
Held for Document Update by: Sean Turner
Date Held: 2010-08-06
Section 8.2.3 says:
The sample code presents almost all formal function arguments of type array with predefined (constant) length with this explicit length. Contrary to that, the function prototypes for SHA384_512Reset do not supply the expected size of the formal argument 'H0'. This inconsistency should be corrected -- as in item (18) above. There are two instances of the issue (see item (xx) below for another two similar instances, with the function declarations): (28a) Within the function prototype definition part of the '#ifdef USE_32BIT_ONLY' branch of the sample code, near the bottom of page 50, the RFC says: static int SHA384_512Reset(SHA512Context *context, uint32_t H0[]); For consistency and clarity, it should say: static int SHA384_512Reset(SHA512Context *context, uint32_t H0[SHA512HashSize/4]); (28b) Within the function prototype definition part of the '#else /* !USE_32BIT_ONLY */' branch of the sample code, near the bottom of page 51, the RFC says: static int SHA384_512Reset(SHA512Context *context, uint64_t H0[]); For consistency and clarity, it should say: static int SHA384_512Reset(SHA512Context *context, uint64_t H0[SHA512HashSize/8]);