Lines Matching refs:fips

5 fips_module - OpenSSL fips module guide
88     fips = fips_sect
184         OSSL_PROVIDER *fips;
187         fips = OSSL_PROVIDER_load(NULL, "fips");
188         if (fips == NULL) {
194             OSSL_PROVIDER_unload(fips);
202         OSSL_PROVIDER_unload(fips);
236 standards you can specify the property query C<fips=yes> like this:
240     sha256 = EVP_MD_fetch(NULL, "SHA2-256", "fips=yes");
254 example sets the default property query of C<fips=yes> for all fetches within
257     EVP_set_default_properties(NULL, "fips=yes");
267 implementation to be fetched from, e.g. C<provider=default> or C<provider=fips>.
270 There is also the C<fips> property. All FIPS algorithms match against the
271 property query C<fips=yes>. There are also some non-cryptographic algorithms
272 available in the default and base providers that also have the C<fips=yes>
280 sets the default property value to be C<fips=yes>. Note that this config file
294     fips = fips_sect
301     default_properties = fips=yes
308 called F<openssl-fips.cnf> that automatically loads and configures the FIPS and
317      * Create two nondefault library contexts. One for fips usage and
318      * one for non-fips usage
333     if (!OSSL_LIB_CTX_load_config(fips_libctx, "openssl-fips.cnf"))
401 therefore these encoders/decoders have the C<fips=yes> property against them.
437      * The "fips=yes" property includes all FIPS approved algorithms
442     SSL_CTX *fips_ssl_ctx = SSL_CTX_new_ex(NULL, "fips=yes", TLS_method());
444      * The "provider!=fips" property allows algorithms from any
447     SSL_CTX *non_fips_ssl_ctx = SSL_CTX_new_ex(NULL, "provider!=fips",