Lines Matching refs:from
22 * The legacy API `mbedtls_xxx` is inherited from PolarSSL.
25 Mbed TLS is gradually shifting from the legacy API to the PSA API. Mbed TLS 4.0 will be the first v…
158 * Benefiting from a PSA accelerator, or from PSA's world separation, even without `MBEDTLS_USE_PSA_…
160 …from an `mbedtls_pk_context`. This partially exists in the form of `mbedtls_pk_wrap_as_opaque`, bu…
192 …lt to predict exactly what parameters are needed. For example, converting from an ASN.1 ECDSA sign…
217 …0) Move `mbedtls_md_psa_alg_from_type` and `mbedtls_md_type_from_psa_alg` from `library/md_psa.h` …
247 #### API to create a PSA key from a PK context
253 When creating a PSA key, apart from the key material, the key is determined by attributes, which fa…
255 * Type and size. These are directly related to the key material and can be deduced from it if the k…
256 …from the `mbedtls_pk_context` object. Just choosing one algorithm is problematic because it doesn'…
257 * Persistence and location. This is completely orthogonal to the information from the `mbedtls_pk_c…
261 …PSA key has exactly two algorithms, and also allows the caller to benefit from default for the pol…
285 …and `PSA_ALG_RSA_OAEP(hash)` for an encrypt/decrypt usage where `hash` is from the RSA key's param…
289 …sponding public-key type, and remove private-key usage flags from the usage flags read from the ex…
314 …on to switch to PSA for creating the key material (for example to benefit from a PSA accelerator d…
344 …d [providing the functions from the ASN.1 module](https://github.com/Mbed-TLS/mbedtls/pull/8703). …