Lines Matching refs:example
10 G2. Allow isolation of long-term secrets (for example, private keys).
11 G3. Allow isolation of short-term secrets (for example, TLS session keys).
126 example `mbedtls_cipher_mode_t` and its values). The
190 This strategy is not useful when no context is used, for example with the
266 working on other parts such as X.509 and TLS - for example, a configuration
270 work is divided into PRs, sometimes not. For example, in situations where it's
284 ciphers. For example,`ctr_drbg.c` calls the legacy API `mbedtls_aes`.
306 convenient, for example in parts of the code that accept old-style identifiers
313 to that module (for example, TLS identifiers of curves and there conversion
320 `PSA_WANT_xxx` macros. For example, PSA-based code that want to use SHA-256
332 code that should always use `PSA_WANT`). For example, for hashes this is the
348 that build and run tests in newly-supported configurations. For example, if
390 runtime, RAM usage or code size penalty), for example just a bunch of
393 Unfortunately that's unlikely to fully work. For example, the MD layer uses the
400 incomplete (for example, for MD covering only hashes, or for Cipher covering
401 only AEAD) or differs significantly from the existing API (for example,
408 cost. For example, `mbedtls_md_context_t` would be defined as a (tagged) union
417 be a temporary solution: for example keep the compatibility layers in 4.0 (and
428 `MBEDTLS_USE_PSA_CRYPTO` is defined) For example, when parsing a large
429 number, N, of X.509 certificates (for example the list of trusted roots), it
444 identifiers, for example `#define MBEDTLS_MD_SHA256 PSA_ALG_SHA_256`; most of
447 example identifiers for elliptic curves.
463 1. APIs that rely on a legacy `mbedtls_` crypto type: for example
470 2. APIs the accept list of identifiers: for example