Lines Matching refs:not
39 `mbedtls/mbedtls_config.h`. This ensures the built-in implementation is not
94 to low-level hash APIs (`mbedtls_sha256()` etc.) are not possible for the
122 (`mbedtls_sha256()` etc.) will not be possible for the legacy modules that
129 `PSA_WANT_ALG_DETERMINISTIC_ECDSA` on the PSA one) to be not available.
183 - direct calls to APIs from the disabled modules are not possible;
184 - PK, X.509 and TLS will not support restartable ECC operations (see
210 curve is identified not by name, but by explicit parameters;
217 result in some code size savings, but not as much as when none of the
228 consequence these are not supported in builds without `MBEDTLS_ECDSA_C`.
231 are not supported without `ECDH_C`. See also limitations regarding
235 Again, we have plans to support this in the future but not with an established
255 `KEY_PAIR_EXPORT` but not `KEY_PAIR_GENERATE`. (Note: currently the driver
256 interface does not support `KEY_PAIR_DERIVE`.)
364 is enabled but not accelerated, then all key types that can be used with it
366 - If a key type is enabled but not accelerated, then all algorithms that can be
396 (i.e. `PSA_WANT_xxx`) symbols is not always 1:1. For example:
422 - Use CCM and GCM via legacy functions `mbedtls_[ccm|gcm]_xxx()` (but not the
435 - The legacy AES module (`MBEDTLS_AES_C`) is not enabled and
444 - The application is not using the `mbedtls_cipher_` API.
454 - Encryption/decryption functions from the PKCS5 and PKCS12 module will not be
458 Note: AEAD ciphers (CCM, GCM, ChachaPoly) do not have a dependency on