ctr_drbg: Clarify reseed_counter values before seeding
Before the initial seeding, reseed_counter used to always be 0. Now, the value depends on whether or not the user has explicitly set the amount of data to get from the nonce (via e.g. mbedtls_ctr_drbg_set_nonce_len()). Add comments to clarify the possible values reseed_counter can have before the initial seeding.
This commit is contained in:
parent
448d1cc854
commit
a15c71374b
1 changed files with 3 additions and 1 deletions
|
@ -177,7 +177,9 @@ typedef struct mbedtls_ctr_drbg_context
|
||||||
* minus one.
|
* minus one.
|
||||||
* Before the initial seeding, this field
|
* Before the initial seeding, this field
|
||||||
* contains the amount of entropy in bytes
|
* contains the amount of entropy in bytes
|
||||||
* to use as a nonce for the initial seeding.
|
* to use as a nonce for the initial seeding,
|
||||||
|
* or -1 if no nonce length has been explicitly
|
||||||
|
* set (see mbedtls_ctr_drbg_set_nonce_len()).
|
||||||
*/
|
*/
|
||||||
int prediction_resistance; /*!< This determines whether prediction
|
int prediction_resistance; /*!< This determines whether prediction
|
||||||
resistance is enabled, that is
|
resistance is enabled, that is
|
||||||
|
|
Loading…
Reference in a new issue