Also mention HMAC_DRBG in the changelog entry

There were no tricky compliance issues for HMAC_DBRG, unlike CTR_DRBG,
but mention it anyway. For CTR_DRBG, summarize the salient issue.
This commit is contained in:
Gilles Peskine 2019-09-30 15:25:18 +02:00
parent 0b5e804c09
commit 6735363f80

View File

@ -3,8 +3,9 @@ mbed TLS ChangeLog (Sorted per branch, date)
= mbed TLS 2.16.x branch released xxxx-xx-xx = mbed TLS 2.16.x branch released xxxx-xx-xx
Changes Changes
* Clarify how the interface of the CTR_DRBG module relates to * Clarify how the interface of the CTR_DRBG and HMAC modules relates to
NIST SP 800-90A. NIST SP 800-90A. In particular CTR_DRBG requires an explicit nonce
to achieve a 256-bit strength if MBEDTLS_ENTROPY_FORCE_SHA256 is set.
= mbed TLS 2.16.3 branch released 2019-09-06 = mbed TLS 2.16.3 branch released 2019-09-06