Lines Matching refs:not
43 - it's not fully compatible with `MBEDTLS_ECP_RESTARTABLE`: you can enable
74 Currently this option controls not only the presence of restartable APIs in
76 Crypto does not support restartable operations, there's a clear conflict: the
81 added to PSA in Mbed TLS 3.4, but support for ECDH is not present yet.
88 1. Existing applications may not be calling `psa_crypto_init()` before using
93 2. It's currently not possible to enable `MBEDTLS_PSA_CRYPTO_C` in
112 Taking advantage of the existing abstractions layers - or not
122 Note: key exchange (FFDH, ECDH) is not covered by an abstraction layer.
129 `MBEDTLS_USE_PSA_CRYPTO` is enabled. (This is not an issue for G1, G2, G3
152 This strategy is not very well suited to the Cipher layer, as the PSA
157 signatures in the format that X.509 & TLS want) are not covered by PSA, so
160 part is not covered by PSA yet, if we decide to do that.)
183 be changed when setting up the context, but not when using it. In
190 This strategy is not useful when no context is used, for example with the
244 Criterion (c) ensures not only test coverage, but that driver-based builds are
251 dispatch to PSA, but not the low-level legacy API, for all operations.
254 2. Have users of these algorithms not depend on the legacy API for information
260 Note: the first two steps enable use of drivers, but not by themselves removal
263 Note: the fact that step 1 is not achieved for all of libmbedcrypto (see
270 work is divided into PRs, sometimes not. For example, in situations where it's
271 not possible to achieve good test coverage at the end of step 1 or step 2, it
282 MD (not low-level hash APIs), which then dispatches to PSA if applicable.
283 - Step 1 is not achieved for all of the crypto library when it come to
305 for information management as well. However sometimes it may not be
314 to/from PSA or legacy identifiers belongs in TLS, not `ecp.c`).
345 Since supporting driver-only builds is not about adding features, but about
346 supporting existing features in new types of builds, testing will not involve
356 taken to ensure this does not happen. The following criteria can be used:
415 Since this would still represent a non-zero cost, not only in terms of code
438 from/to various formats, which is currently not fully covered by the PSA