Lines Matching refs:load
122 If applications take explicit steps to not load the default config file or
163 Applications may choose to load the FIPS provider explicitly rather than relying
173 This means all the required config information will be available to load the
186 printf("Failed to load FIPS provider\n");
192 printf("Failed to load base provider\n");
207 later explicitly load the FIPS provider then you will have both the FIPS and the
217 decoding keys. If you decide not to load the default provider then you
218 will usually want to load the base provider instead.
278 does not load the "base" provider. All supporting algorithms that are in "base"
328 * providers so we don't need to explicitly load them here.
334 * We don't need to do anything special to load the default
367 Note that we have made use of the special "null" provider here which we load
375 particular operation. To be sure this doesn't happen you can load the "null"
377 explicitly loaded, the default provider will not automatically load. This means
408 in libssl. If you are using a nondefault library context to load the FIPS