Lines Matching refs:where
15 * [OPEN] Open question: a specific aspect of the design where there are several plausible decisions.
25 …rom the legacy API to the PSA API. Mbed TLS 4.0 will be the first version where the PSA API is con…
63 * Manipulating data formats, other than keys, where the PSA API is lacking.
73 …specially enums and functions) that they provide, listing PSA equivalents where they exist. There …
78 Based on “[Where mixing happens](#where-mixing-happens)”, we focus the gap analysis on two topics: …
147 There are several scenarios where an application has a legacy key pair or public key (`mbedtls_pk_c…
149 Reasons for first creating a legacy key object, where it's impossible or impractical to directly cr…
151 * A very common case where the input is a legacy key object is parsing. PSA does not (yet) have an …
164 There are several scenarios where an application has a PSA key and needs to use it through an inter…
211 * Mention it where relevant in the PSA transition guide.
275 …* [OPEN] Or should it reset them to 0? Resetting is more convenient for the case where the pk key …
285 …n/verify usage, and `PSA_ALG_RSA_OAEP(hash)` for an encrypt/decrypt usage where `hash` is from the…