Lines Matching refs:API

88 The option `MBEDTLS_USE_PSA_CRYPTO` causes parts of the library to call the PSA API instead of lega…
118 * ECDSA (HMAC\_DRBG; `md.h` exposed through API)
119 * ECJPAKE (hashes via MD-light; `md.h` exposed through API)
121 * HKDF (HMAC via `md.h`; `md.h` exposed through API)
122 * HMAC\_DRBG (hashes and HMAC via `md.h`; `md.h` exposed through API)
124 * PKCS5 (HMAC via `md.h`; `md.h` exposed through API)
126 * RSA (hash via MD-light for PSS and OAEP; `md.h` exposed through API)
145   * Note: `cipher.h` exposed through API.
154   * Currently using low-level non-generic API (`aes.h`).
180   * Note: `cipher.h` exposed through API.
195 …unctions that are called after the keystore lookup, rather than to the PSA API functions (but this…
213 If `PSA_WANT_xxx` is disabled, this should guarantee that attempting xxx through the PSA API will f…
265 …t call `mbedtls_sha256`, it's all there is, and it doesn't matter (from an API perspective) exactl…
320 * We can optimize `md.c` without making API changes to `md.h`.
354 …ds due to its smaller block size) and CTR-DRBG directly uses the low-level API from `aes.h`. In al…
366 …CM may either be a new internal module, or a subset of the existing Cipher API, extended with the …
368 Reasons for making this layer's API a subset of the existing Cipher API:
374 Possible costs of re-using (a subset of) the existing Cipher API instead of defining a new one:
379 - significant differences in how the `cipher.h` API is implemented between builds with the full Cip…
579 The following API functions are offered: