Fix typo in documentation (CTR warning)

This commit is contained in:
Manuel Pégourié-Gonnard 2018-03-01 13:48:21 +01:00
parent 21662148f7
commit f6b787cbcc
4 changed files with 4 additions and 4 deletions

View File

@ -314,7 +314,7 @@ int mbedtls_aes_crypt_cfb8( mbedtls_aes_context *ctx,
* 2. Use a randomly-generated \p nonce_counter for each call.
* With this strategy, you need to ensure the nonce is generated
* in an unbiased way and you must not encrypt more than 2**64
* block of data.
* blocks of data.
*
* Note that for both stategies, the limit is in number of blocks
* and that an AES block is 16 bytes.

View File

@ -262,7 +262,7 @@ int mbedtls_aria_crypt_cfb128( mbedtls_aria_context *ctx,
* 2. Use a randomly-generated \p nonce_counter for each call.
* With this strategy, you need to ensure the nonce is generated
* in an unbiased way and you must not encrypt more than 2**64
* block of data.
* blocks of data.
*
* Note that for both stategies, the limit is in number of blocks
* and that an ARIA block is 16 bytes.

View File

@ -184,7 +184,7 @@ int mbedtls_blowfish_crypt_cfb64( mbedtls_blowfish_context *ctx,
* 2. Use a randomly-generated \p nonce_counter for each call.
* With this strategy, you need to ensure the nonce is generated
* in an unbiased way and you must not encrypt more than 2**32
* block of data.
* blocks of data.
*
* Note that for both stategies, the limit is in number of blocks
* and that a Blowfish block is 8 bytes.

View File

@ -201,7 +201,7 @@ int mbedtls_camellia_crypt_cfb128( mbedtls_camellia_context *ctx,
* 2. Use a randomly-generated \p nonce_counter for each call.
* With this strategy, you need to ensure the nonce is generated
* in an unbiased way and you must not encrypt more than 2**64
* block of data.
* blocks of data.
*
* Note that for both stategies, the limit is in number of blocks
* and that a CAMELLIA block is 16 bytes.