Add missing backticks
Signed-off-by: Dave Rodgman <dave.rodgman@arm.com>
This commit is contained in:
parent
7d2ac88f93
commit
a014831732
1 changed files with 11 additions and 11 deletions
|
@ -217,25 +217,25 @@ of this option for details.
|
||||||
|
|
||||||
### Separated `MBEDTLS_SHA224_C` and `MBEDTLS_SHA256_C`
|
### Separated `MBEDTLS_SHA224_C` and `MBEDTLS_SHA256_C`
|
||||||
|
|
||||||
This does not affect users who use the default `mbedtls_config.h`. MBEDTLS_SHA256_C
|
This does not affect users who use the default `mbedtls_config.h`. `MBEDTLS_SHA256_C`
|
||||||
was enabled by default. Now both MBEDTLS_SHA256_C and MBEDTLS_SHA224_C are
|
was enabled by default. Now both `MBEDTLS_SHA256_C` and `MBEDTLS_SHA224_C` are
|
||||||
enabled.
|
enabled.
|
||||||
|
|
||||||
If you were using custom config file with MBEDTLS_SHA256_C enabled, then
|
If you were using custom config file with `MBEDTLS_SHA256_C` enabled, then
|
||||||
you will need to add `#define MBEDTLS_SHA224_C` option to your config.
|
you will need to add `#define MBEDTLS_SHA224_C` option to your config.
|
||||||
Current version of the library does not support enabling MBEDTLS_SHA256_C
|
Current version of the library does not support enabling `MBEDTLS_SHA256_C`
|
||||||
without MBEDTLS_SHA224_C.
|
without `MBEDTLS_SHA224_C`.
|
||||||
|
|
||||||
### Replaced `MBEDTLS_SHA512_NO_SHA384` with `MBEDTLS_SHA384_C`
|
### Replaced `MBEDTLS_SHA512_NO_SHA384` with `MBEDTLS_SHA384_C`
|
||||||
|
|
||||||
This does not affect users who use the default `mbedtls_config.h`.
|
This does not affect users who use the default `mbedtls_config.h`.
|
||||||
MBEDTLS_SHA512_NO_SHA384 was disabled by default, now MBEDTLS_SHA384_C is
|
`MBEDTLS_SHA512_NO_SHA384` was disabled by default, now `MBEDTLS_SHA384_C` is
|
||||||
enabled by default.
|
enabled by default.
|
||||||
|
|
||||||
If you were using a config file with both MBEDTLS_SHA512_C and
|
If you were using a config file with both `MBEDTLS_SHA512_C` and
|
||||||
MBEDTLS_SHA512_NO_SHA384, then just remove the MBEDTLS_SHA512_NO_SHA384.
|
MBEDTLS_SHA512_NO_SHA384, then just remove the `MBEDTLS_SHA512_NO_SHA384`.
|
||||||
If you were using a config file with MBEDTLS_SHA512_C and without
|
If you were using a config file with `MBEDTLS_SHA512_C` and without
|
||||||
MBEDTLS_SHA512_NO_SHA384 and you need the SHA-384 algorithm, then add
|
`MBEDTLS_SHA512_NO_SHA384` and you need the SHA-384 algorithm, then add
|
||||||
`#define MBEDTLS_SHA384_C` to your config file.
|
`#define MBEDTLS_SHA384_C` to your config file.
|
||||||
|
|
||||||
### GCM multipart interface: application changes
|
### GCM multipart interface: application changes
|
||||||
|
@ -532,7 +532,7 @@ function.
|
||||||
The API is changed to include the parameter `critical` which enables marking an
|
The API is changed to include the parameter `critical` which enables marking an
|
||||||
extension included in a CSR as critical. To get the previous behavior pass 0.
|
extension included in a CSR as critical. To get the previous behavior pass 0.
|
||||||
|
|
||||||
### Remove the config option MBEDTLS_X509_ALLOW_UNSUPPORTED_CRITICAL_EXTENSION
|
### Remove the config option `MBEDTLS_X509_ALLOW_UNSUPPORTED_CRITICAL_EXTENSION`
|
||||||
|
|
||||||
This change does not affect users of the default configuration; it only affects
|
This change does not affect users of the default configuration; it only affects
|
||||||
users who enable this option.
|
users who enable this option.
|
||||||
|
|
Loading…
Reference in a new issue