Lines Matching refs:algorithm
220 * How to decide whether a specific algorithm or key type is supported (eventually based on `MBEDTLS…
227 * Some parameter indicating which algorithm to use.
242 …which hash algorithm to use based on a parameter of type `mbedtls_md_type_t`. (More generally, all…
266 …` is not enabled, but xxx is enabled through PSA, then a request to use algorithm xxx through some…
269 …algorithm is available through the legacy domain, only through the PSA domain. What does this mean…
281 * A legacy hash interface is available and the hash algorithm is implemented in software.
282 * PSA crypto is enabled and the hash algorithm is implemented via PSA.
297 … `psa_crypto_init()` has been called, without having to inspect the specifics of algorithm support.
304 Requirements: given a hash algorithm,
417 …tls_md_info_t *` because this arises when you try to use an unsupported algorithm (`mbedtls_md_inf…
419 #### MD algorithm support macros
421 For each hash algorithm, `md.h` defines a macro `MBEDTLS_MD_CAN_xxx` whenever the corresponding has…
472 The `engine` field is almost redundant with knowledge about `type`. However, when an algorithm is a…
499 …afe: whether it returns 0 or 1, you can call a PSA hash function on the algorithm and it will retu…
507 If given an algorithm as an `mbedtls_md_type_t type` (possibly being the `type` field of a `const m…
523 > If an algorithm has a legacy implementation, it is also available through PSA.
562 So far, MD light only dispatches to PSA if an algorithm is available via `MBEDTLS_PSA_CRYPTO_C`, no…
603 The `engine` field is almost redundant with knowledge about `type`. However, when an algorithm is a…