Lines Matching refs:algorithm
27 referred to in OpenSSL as "algorithms". Each algorithm may have multiple
28 implementations available for use. For example the RSA algorithm is available as
40 encryption operation using AES (or any other encryption algorithm) you would use
47 A provider in OpenSSL is a component that collects together algorithm
48 implementations. In order to use an algorithm you must have at least one
102 In order to use an algorithm an implementation for it must first be "fetched".
112 When fetching an algorithm it is possible to specify a property query string to
115 algorithm implementations in the default provider.
128 Users of the OpenSSL libraries never query a provider directly for an algorithm
130 functions that do the work, and they return an appropriate algorithm object back
133 be used to explicitly fetch a digest algorithm implementation. The user is
153 For all currently implemented fetching functions this is the algorithm name.
157 The property query string used to guide selection of the algorithm
162 The algorithm implementation that is fetched can then be used with other diverse
169 OpenSSL has a number of functions that return an algorithm object with no
179 In some cases implicit fetching can also occur when a NULL algorithm parameter
180 is supplied. In this case an algorithm implementation is implicitly fetched
181 using default search criteria and an algorithm name that is consistent with
215 The following section provides a series of examples of fetching algorithm
264 the "whirlpool" algorithm is in the "legacy" provider. Also note that the
287 algorithm identifier to the appropriate fetching function. Also see the provider
297 contains all of the most commonly used algorithm implementations. Should it be
312 algorithm implementations for encoding and decoding for OpenSSL keys.
316 Some encoding and decoding algorithm implementations are not FIPS algorithm
327 (see L<config(5)>). It contains algorithm implementations that have been
331 these implementations. All approved algorithm implementations in the FIPS
333 may also contain non-approved algorithm implementations and these can be
342 (see L<config(5)>). It contains algorithm implementations that are considered
400 * Fetch the SHA256 algorithm implementation for doing the digest. We're
460 Encoders and decoders are just algorithm implementations in the same way as
461 any other algorithm implementation in OpenSSL. They are implemented by