Lines Matching refs:when
45 I want to have clear rules for when to use which interface,
92 …when this will actually work](#why-psa-is-not-always-possible). This effectively brings those modu…
93 * Call PSA when a covered module calls a non-covered module which calls another module, for example…
108 …when possible](#why-psa-is-not-always-possible). This consists of the constructed cryptographic pr…
109 * **PSA domain**: includes pk, X.509 and TLS when `MBEDTLS_USE_PSA_CRYPTO` is enabled. Also TLS 1.3…
138 (when called from pkparse).
255 …led. In some limited cases, such as `test_suite_psa_crypto_not_supported` when PSA implements RSA-…
288 …rted (users are not supposed to manually define PSA configuration symbols when `MBEDTLS_PSA_CRYPTO…
291 …anisms available through PSA but not legacy: this allows saving code size when an accelerator is p…
293 …when `MBEDTLS_PSA_CRYPTO_C` is enabled. This would only save at best a very small amount of code s…
314 * The md module has some legacy baggage dating from when it was more open, which we don't care abou…
332 This will go away naturally in 4.0 when this macros is not longer an option (because it's always on…
417 … support null pointers as `const mbedtls_md_info_t *` because this arises when you try to use an u…
421 …ponding hash is available through MD light. These macros are only defined when `MBEDTLS_MD_LIGHT` …
472 … when an algorithm is available both via a legacy module and a PSA accelerator, we will choose bas…
574 it (namely: CCM, GCM) only when `CIPHER_C` is not available, or the new module
603 … when an algorithm is available both via a legacy module and a PSA accelerator, we will choose bas…