Lines Matching refs:one
21 More precisely, we consider such a system where our PSA Crypto implementation is running inside one…
86 … to take into account? Although this extends the possible behaviors of the one-shot interface, the…
142 …ed TLS: almost all API functions have multiple underlying implementations, one for each algorithm.…
157 …one with a size limit that is known at compile time, and small enough that copying the data is not…
170 …tted data, and for all specified algorithms, it is natural to process the input one byte at a time.
190 * when encrypting with an encrypt-and-authenticate or authenticate-then-encrypt structure (one read…
191 * when decrypting with an encrypt-then-authenticate structure (one read to decrypt and one read to …
192 * with SIV modes (not yet present in the PSA API, but likely to come one day) (one full pass to cal…
256 * Any test hooks need only be added in one place.
257 * Copying code must only be reviewed for correctness in one place, rather than in all functions whe…
267 Multipart APIs may follow one of 2 possible approaches for copying of input:
271 This is simple and mirrors the approach for one-shot APIs nicely. However, allocating memory in the…
279 …icated than approach (1) and introduces some extra issues. For example, if one of the intermediate…
357 … This would be achieved by replacing the implementation of `malloc()` with one that allocates pois…
544 With these structs we may create 2 pairs of functions, one pair for input copies: