Lines Matching full:fetch

111 Explicit fetching involves directly calling a specific API to fetch an algorithm
115 can be used to explicitly fetch a digest algorithm implementation. The user is
172 \&\fBEVP_DigestSignInit\fR\|(3), all fetch the implementations implicitly. Usually the
173 algorithm to fetch is determined based on the type of key that is being used and
178 recommended to use a single explicit fetch of the algorithm and then reuse the
191 fetch will use an internally cached prefetched object, but it will
197 Fetch a message digest/hashing algorithm implementation.
200 Fetch a symmetric cipher algorithm implementation.
203 Fetch a Key Derivation Function (KDF) algorithm implementation.
206 Fetch a Message Authentication Code (MAC) algorithm implementation.
209 Fetch a Key Encapsulation Mechanism (KEM) algorithm implementation
212 Fetch an encoder algorithm implementation (e.g. to encode keys to a specified
216 Fetch a decoder algorithm implementation (e.g. to decode keys from a specified
220 Fetch a Pseudo Random Number Generator (PRNG) algorithm implementation.
232 Fetch any available implementation of SHA2\-256 in the default context. Note
241 Fetch any available implementation of AES\-128\-CBC in the default context:
249 Fetch an implementation of SHA2\-256 from the default provider in the default
258 Fetch an implementation of SHA2\-256 that is not from the default provider in the
267 Fetch an implementation of SHA2\-256 that is preferably from the FIPS provider in
276 Fetch an implementation of SHA2\-256 from the default provider in the specified
285 Load the legacy provider into the default context and then fetch an
360 \&      * Fetch the SHA256 algorithm implementation for doing the digest. We\*(Aqre
365 \&      * In a larger application this fetch would just be done once, and could