Lines Matching full:fetch

58 Explicit fetching involves directly calling a specific API to fetch an algorithm
62 can be used to explicitly fetch a digest algorithm implementation. The user is
127 L<EVP_DigestSignInit(3)>, all fetch the implementations implicitly. Usually the
128 algorithm to fetch is determined based on the type of key that is being used and
134 recommended to use a single explicit fetch of the algorithm and then reuse the
147 fetch will use an internally cached prefetched object, but it will
156 Fetch a message digest/hashing algorithm implementation.
160 Fetch a symmetric cipher algorithm implementation.
164 Fetch a Key Derivation Function (KDF) algorithm implementation.
168 Fetch a Message Authentication Code (MAC) algorithm implementation.
172 Fetch a Key Encapsulation Mechanism (KEM) algorithm implementation
176 Fetch an encoder algorithm implementation (e.g. to encode keys to a specified
181 Fetch a decoder algorithm implementation (e.g. to decode keys from a specified
186 Fetch a Pseudo Random Number Generator (PRNG) algorithm implementation.
201 Fetch any available implementation of SHA2-256 in the default context. Note
208 Fetch any available implementation of AES-128-CBC in the default context:
214 Fetch an implementation of SHA2-256 from the default provider in the default
221 Fetch an implementation of SHA2-256 that is not from the default provider in the
228 Fetch an implementation of SHA2-256 that is preferably from the FIPS provider in
235 Fetch an implementation of SHA2-256 from the default provider in the specified
242 Load the legacy provider into the default context and then fetch an
314       * Fetch the SHA256 algorithm implementation for doing the digest. We're
319       * In a larger application this fetch would just be done once, and could