Lines Matching refs:will
34 means the algorithm will be available in the PSA Crypto API.
50 `MBEDTLS_USE_PSA_CRYPTO` is enabled, so in most cases your application will
93 APIs), as well as X.509 and TLS, will work as usual, except that direct calls
122 (`mbedtls_sha256()` etc.) will not be possible for the legacy modules that
179 In such builds, all crypto operations via the PSA Crypto API will work as
184 - PK, X.509 and TLS will not support restartable ECC operations (see
204 A limited subset of `ecp.c` will still be automatically re-enabled if any of
214 Note: when any of the above options is enabled, a subset of `ecp.c` will
216 you can still disable `MBEDTLS_ECP_C` in `mbedtls_config.h` and this will
249 algorithms will be disabled, provided all the requested curves and key types
293 `MBEDTLS_PKCS1_V21`, and RSA will still work in PSA Crypto.
298 PSA Crypto works. In particular, PK, X.509 and TLS will _not_ work with
351 will work, as well as X.509 and TLS (with `MBEDTLS_USE_PSA_CRYPTO` enabled) but
352 some non-PSA APIs will be absent or have reduced functionality, see
360 will need to be built-in.
362 used with it will need to be built-in.
364 Some legacy modules can't take advantage of PSA drivers yet, and will either
372 is enabled, then only the corresponding cipher will be available at runtime
375 without `MBEDTLS_CMAC_C` and CMAC will be usable with `psa_max_xxx` APIs.)
376 - `MBEDTLS_CIPHER_C`: the `mbedtls_cipher_xxx()` APIs will only work with
380 - `MBEDTLS_PKCS5_C`: encryption/decryption (PBES2, PBE) will only work with
382 - PEM decryption will only work with ciphers that are built-in.
383 - PK parse will only be able to parse encrypted keys using built-in ciphers.
385 Note that if you also disable `MBEDTLS_CIPHER_C`, there will be additional
447 In such a build, everything will work as usual except for the following:
449 - Encryption/decryption functions from the PKCS5 and PKCS12 module will not be
451 - Parsing of PKCS5- or PKCS12-encrypted keys in PK parse will fail.