lib/mbedtls
1
0
Fork 0
mirror of https://github.com/Mbed-TLS/mbedtls.git synced 2025-07-30 22:43:08 +03:00
Code Activity

Update documentation to mention ECC drivers

Browse Source 
Signed-off-by: Manuel Pégourié-Gonnard <manuel.pegourie-gonnard@arm.com>
This commit is contained in:
Manuel Pégourié-Gonnard
2023-03-29 10:30:26 +02:00
parent 77902df54a
commit 93b21e74f9
2 changed files with 13 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/use-psa-crypto.md
View File

@ -15,6 +15,13 @@ General considerations
`psa_crypto_init()` before calling any function from the SSL/TLS, X.509 or PK `psa_crypto_init()` before calling any function from the SSL/TLS, X.509 or PK
module. module.
**Why enable this option:** to fully take advantage of PSA drivers in PK,
X.509 and TLS. For example, enabling this option is what allows use of drivers
for ECDSA, ECDH and EC J-PAKE in those modules. However, note that ven with
this option disabled, some code in PK, X.509, TLS or the crypto library might
still use PSA drivers, if it can determine it's safe to do so; currently
that's the case for hashes.
**Relationship with other options:** This option depends on **Relationship with other options:** This option depends on
`MBEDTLS_PSA_CRYPTO_C`. These two options differ in the following way: `MBEDTLS_PSA_CRYPTO_C`. These two options differ in the following way:
- `MBEDTLS_PSA_CRYPTO_C` enables the implementation of the PSA Crypto API. - `MBEDTLS_PSA_CRYPTO_C` enables the implementation of the PSA Crypto API.

9
include/mbedtls/mbedtls_config.h
View File

@ -1933,9 +1933,12 @@
* \warning If you enable this option, you need to call `psa_crypto_init()` * \warning If you enable this option, you need to call `psa_crypto_init()`
* before calling any function from the SSL/TLS, X.509 or PK modules. * before calling any function from the SSL/TLS, X.509 or PK modules.
* *
* \note Even with this option disabled, some code in PK, X.509, TLS or the * \note An important and desirable effect of this option is that it allows
* crypto library might still use PSA drivers, if it can determine it's safe * PK, X.509 and TLS to take advantage of PSA drivers. For example, enabling
* to do so. * this option is what allows use of drivers for ECDSA, ECDH and EC J-PAKE in
* those modules. However, note that ven with this option disabled, some code
* in PK, X.509, TLS or the crypto library might still use PSA drivers, if it
* can determine it's safe to do so; currently that's the case for hashes.
* *
* \note See docs/use-psa-crypto.md for a complete description this option. * \note See docs/use-psa-crypto.md for a complete description this option.
* *