Lines Matching refs:when
9 G1. Use PSA Crypto drivers when available.
13 G5. Code size: compile out our implementation when a driver is available.
15 As of Mbed TLS 3.2, most of (G1) and all of (G2) is implemented when
128 particular in existing structures and public APIs, even when
183 be changed when setting up the context, but not when using it. In
186 - Upside: avoids dependency loop when PSA implemented on top of that layer.
187 - Downside: when the context is typically set up by the application, requires
190 This strategy is not useful when no context is used, for example with the
225 - MD (G5): silently call PSA when a driver is available, see
233 software implementation when a driver is available.
265 configuration", to allow working around internal crypto dependencies when
278 - Step 1 is achieved for most of PK, X.509, and TLS when
283 - Step 1 is not achieved for all of the crypto library when it come to
285 - Step 2 is achieved for most of X.509 and TLS (same gaps as step 1) when
304 The most satisfying situation here is when we can just use the PSA Crypto API
350 drivers when `MBEDTLS_USE_PSA_CRYPTO` is defined, there should be a place in
424 Note: when it comes to holding public keys in the PK layer, depending on how
427 slot only when needed (see current `ecdsa_verify_wrap` when
428 `MBEDTLS_USE_PSA_CRYPTO` is defined) For example, when parsing a large
434 when it's actually used.
481 An question that needs careful consideration when we come around to removing