mirror of
https://github.com/Mbed-TLS/mbedtls.git
synced 2025-07-29 11:41:15 +03:00
Merge pull request #5850 from bootstrap-prime/mbedtls-2.28
Fix typos in documentation and constants with typo finding tool
This commit is contained in:
@ -828,7 +828,7 @@ static int ctr_drbg_self_test_entropy( void *data, unsigned char *buf,
|
||||
return( 1 ); \
|
||||
}
|
||||
|
||||
#define SELF_TEST_OUPUT_DISCARD_LENGTH 64
|
||||
#define SELF_TEST_OUTPUT_DISCARD_LENGTH 64
|
||||
|
||||
/*
|
||||
* Checkup routine
|
||||
@ -854,7 +854,7 @@ int mbedtls_ctr_drbg_self_test( int verbose )
|
||||
(void *) entropy_source_pr,
|
||||
pers_pr, MBEDTLS_CTR_DRBG_KEYSIZE ) );
|
||||
mbedtls_ctr_drbg_set_prediction_resistance( &ctx, MBEDTLS_CTR_DRBG_PR_ON );
|
||||
CHK( mbedtls_ctr_drbg_random( &ctx, buf, SELF_TEST_OUPUT_DISCARD_LENGTH ) );
|
||||
CHK( mbedtls_ctr_drbg_random( &ctx, buf, SELF_TEST_OUTPUT_DISCARD_LENGTH ) );
|
||||
CHK( mbedtls_ctr_drbg_random( &ctx, buf, sizeof( result_pr ) ) );
|
||||
CHK( memcmp( buf, result_pr, sizeof( result_pr ) ) );
|
||||
|
||||
@ -879,7 +879,7 @@ int mbedtls_ctr_drbg_self_test( int verbose )
|
||||
(void *) entropy_source_nopr,
|
||||
pers_nopr, MBEDTLS_CTR_DRBG_KEYSIZE ) );
|
||||
CHK( mbedtls_ctr_drbg_reseed( &ctx, NULL, 0 ) );
|
||||
CHK( mbedtls_ctr_drbg_random( &ctx, buf, SELF_TEST_OUPUT_DISCARD_LENGTH ) );
|
||||
CHK( mbedtls_ctr_drbg_random( &ctx, buf, SELF_TEST_OUTPUT_DISCARD_LENGTH ) );
|
||||
CHK( mbedtls_ctr_drbg_random( &ctx, buf, sizeof( result_nopr ) ) );
|
||||
CHK( memcmp( buf, result_nopr, sizeof( result_nopr ) ) );
|
||||
|
||||
|
@ -399,7 +399,7 @@ static int ecdh_read_params_internal( mbedtls_ecdh_context_mbed *ctx,
|
||||
}
|
||||
|
||||
/*
|
||||
* Read the ServerKeyExhange parameters (RFC 4492)
|
||||
* Read the ServerKeyExchange parameters (RFC 4492)
|
||||
* struct {
|
||||
* ECParameters curve_params;
|
||||
* ECPoint public;
|
||||
|
@ -51,7 +51,7 @@
|
||||
* the function's behavior is entirely undefined.
|
||||
* In addition to state integrity, all MPS structures have a more refined
|
||||
* notion of abstract state that the API operates on. For example, all layers
|
||||
* have a notion of 'abtract read state' which indicates if incoming data has
|
||||
* have a notion of 'abstract read state' which indicates if incoming data has
|
||||
* been passed to the user, e.g. through mps_l2_read_start() for Layer 2
|
||||
* or mps_l3_read() in Layer 3. After such a call, it doesn't make sense to
|
||||
* call these reading functions again until the incoming data has been
|
||||
|
Reference in New Issue
Block a user