Lines Matching full:provider

105 also activates the "base" provider. The base provider does not include any
133 that are available in the default OpenSSL Provider.
166 Applications may choose to load the FIPS provider explicitly rather than relying
169 in this case we do not automatically activate the FIPS provider via that config
178 FIPS provider can then be loaded programmatically like this:
180 #include <openssl/provider.h>
189 printf("Failed to load FIPS provider\n");
195 printf("Failed to load base provider\n");
208 cryptographic functions before this occurs then, if no provider has yet been
209 loaded, then the default provider will be automatically loaded. If you then
210 later explicitly load the FIPS provider then you will have both the FIPS and the
211 default provider loaded at the same time. It is undefined which implementation
216 Also note that in this example we have additionally loaded the "base" provider.
218 provider - specifically non cryptographic ones which may be used in conjunction
219 with the FIPS provider. For example this contains algorithms for encoding and
220 decoding keys. If you decide not to load the default provider then you
221 will usually want to load the base provider instead.
230 It is possible to have the FIPS provider and other providers (such as the
231 default provider) all loaded at the same time into the same library context. You
247 default provider:
251 sha256 = EVP_MD_fetch(NULL, "SHA2-256", "provider=default");
266 The "provider" property enables you to specify which provider you want an
267 implementation to be fetched from, e.g. C<provider=default> or C<provider=fips>.
268 All algorithms implemented in a provider have this property set on them.
274 can (for example) be used to write out a key generated in the FIPS provider to a
281 does not load the "base" provider. All supporting algorithms that are in "base"
309 base providers. The other library context will just use the default provider.
338 * provider into nonfips_libctx. This happens automatically if no
370 Note that we have made use of the special "null" provider here which we load
379 provider into the default library context. Because a provider has been
380 explicitly loaded, the default provider will not automatically load. This means
402 You should ensure that either the default or base provider is loaded into the
412 provider then you can supply this to libssl using the function
423 * provider loaded has been created called fips_libctx.
428 * provider loaded has been created called non_fips_libctx.
438 * as well as encoders from the default provider that are allowed
444 * The "provider!=fips" property allows algorithms from any
445 * provider except the FIPS provider
447 SSL_CTX *non_fips_ssl_ctx = SSL_CTX_new_ex(NULL, "provider!=fips",
453 provider that implements it. The process is similar for all algorithms. Here the
465 FIPS provider. To determine which versions have undergone
469 provider using one of the validated versions listed there. Normally,
470 it is possible to utilize a FIPS provider constructed from one of the
482 The FIPS module guide was created for use with the new FIPS provider