Lines Matching refs:cipher

107 * **Legacy domain**: does not interact with PSA. Implementations of hashes, of cipher primitives, o…
129 Symmetric ciphers and AEADs (before work on driver-only cipher):
139   * In principle: any cipher-mode (default padding), passed an
145   * Note: `cipher.h` exposed through API.
161   * Note: also called by `cipher.c` if enabled.
167   * Note: also called by `cipher.c` if enabled.
173   * Note: also called by `cipher.c` if enabled.
179   * Note: also called by `cipher.c` if enabled.
180   * Note: `cipher.h` exposed through API.
183   * potentially any cipher/AEAD in any mode and any direction
185 Note: PSA cipher is built on Cipher, but PSA AEAD directly calls the underlying AEAD modules (GCM, …
191 Here are some reasons why calling `psa_xxx()` to perform a hash or cipher calculation might not be …
267 …ciphers, this is more complicated because the cipher functions require the keystore, and plausibly…
338 … do not plan to lift before 4.0, it is acceptable driver-only hashes and cipher support to have th…
342 #### For cipher: prioritize constrained devices and modern TLS
352 ### Dual-dispatch for block cipher primitives
354 …cipher primitive only in the encrypt direction. Currently, GCM and CCM use the Cipher layer in ord…
375 … (Currently the info structure is used for 3 things: (1) to check if the cipher is supported, (2) …
379 - significant differences in how the `cipher.h` API is implemented between builds with the full Cip…
382 …nd cleaner code with a new internal module (see section "Internal "block cipher" abstraction (Ciph…
569 ### Internal "block cipher" abstraction (previously known as "Cipher light")
597 #### Block cipher dual dispatch
601 A block cipher context contains either a legacy module's context (AES, ARIA, Camellia) or a PSA key…