Lines Matching refs:hashes

1 PSA migration strategy for hashes and ciphers
107 * **Legacy domain**: does not interact with PSA. Implementations of hashes, of cipher primitives, o…
115 Hashes and HMAC (after the work on driver-only hashes):
117 * entropy (hashes via MD-light)
119 * ECJPAKE (hashes via MD-light; `md.h` exposed through API)
120 * MD (hashes and HMAC)
122 * HMAC\_DRBG (hashes and HMAC via `md.h`; `md.h` exposed through API)
123 * PKCS12 (hashes via MD-light)
125 * PKCS7 (hashes via MD)
202 …sa_pss_sign()` is called from X.509 code, it should use PSA to calculate hashes. It doesn't, curre…
219 …s encoded (e.g. `mbedtls_md_type_t` vs `const *mbedtls_md_info_t` vs `psa_algorithm_t` for hashes).
246 A natural solution is to double up the encoding of hashes in `mbedtls_md_type_t`. Pass `MBEDTLS_MD_…
250 #### Availability of hashes in RSA-PSS
267 …ation, but we can only do this if the accelerator driver is working. For hashes, it's enough to as…
271 ### Designing an interface for hashes
275 #### Availability of hashes  argument
277 Generalizing the analysis in [“Availability of hashes in RSA-PSS”](#availability-of-hashes-in-RSA-P…
328 We do not need to support driver-only hashes and ciphers in PK. X.509 and TLS without `MBEDTLS_USE_…
330 Note that this applies to TLS 1.3 as well, as some uses of hashes and all uses of ciphers there are…
338 …on which we do not plan to lift before 4.0, it is acceptable driver-only hashes and cipher support…
390 …on interface described in ”[Designing an interface for hashes](#designing-an-interface-for-hashes)…
394 * A [mixed-domain](#classification-of-callers) module that needs to calculate hashes is enabled.
421 …ed when `MBEDTLS_MD_LIGHT` is enabled. Per “[Availability of hashes](#availability-of-hashes)”, `M…
476 MD light needs to support hashes that are only enabled through PSA. Therefore the `mbedtls_md_info_…
558 …r (eliminating the need to a HMAC interface in software if all supported hashes have an accelerato…