Lines Matching refs:load
129 If applications take explicit steps to not load the default config file or
170 Applications may choose to load the FIPS provider explicitly rather than relying
180 This means all the required config information will be available to load the
193 printf("Failed to load FIPS provider\n");
199 printf("Failed to load base provider\n");
214 later explicitly load the FIPS provider then you will have both the FIPS and the
224 decoding keys. If you decide not to load the default provider then you
225 will usually want to load the base provider instead.
285 does not load the "base" provider. All supporting algorithms that are in "base"
335 * providers so we don't need to explicitly load them here.
349 * We don't need to do anything special to load the default
382 Note that we have made use of the special "null" provider here which we load
390 particular operation. To be sure this doesn't happen you can load the "null"
392 explicitly loaded, the default provider will not automatically load. This means
423 in libssl. If you are using a nondefault library context to load the FIPS
