Home
last modified time | relevance | path

Searched refs:validated (Results 1 – 25 of 64) sorted by relevance

123

/freebsd/crypto/openssl/
H A DREADME-FIPS.md5 FIPS validated. The module is implemented as an OpenSSL provider.
10 A cryptographic module is only FIPS validated after it has gone through the complex
13 If you need a FIPS validated module then you must ONLY generate a FIPS provider
34 In order to be FIPS compliant you must only use FIPS validated source code.
36 which versions are FIPS validated. The instructions given below build OpenSSL
37 just using the FIPS validated source code. Any FIPS validated version may be
39 To determine which FIPS validated library version may be appropriate for you.
41 If you want to use a validated FIPS provider, but also want to use the latest
96 Download and build a validated FIPS provider
100 which versions are FIPS validated. For this example we use OpenSSL 3.1.2.
[all …]
H A DREADME.md17 cryptographic module validated to conform with FIPS standards.
137 * [Information about using the OpenSSL FIPS validated module](README-FIPS.md)
H A DREADME-PROVIDERS.md59 It is intended that this provider will be FIPS140-2 validated.
/freebsd/crypto/openssl/doc/man7/
H A Dfips_module.pod103 enabled to prevent accidental use of non-FIPS validated algorithms via broken
358 /* Get a FIPS validated digest */
363 /* Get a non-FIPS validated digest */
421 properties and the default library context to specify usage of FIPS validated
568 The unapproved (non FIPS validated) algorithms have a property query value of
589 Some released versions of OpenSSL do not include a validated
594 provider using one of the validated versions listed there. Normally,
596 validated versions alongside F<libcrypto> and F<libssl> compiled from any
600 As the FIPS provider still supports non-FIPS validated algorithms,
H A DOSSL_PROVIDER-FIPS.pod11 contains an approved set of cryptographic algorithms that is validated by an
551 Some released versions of OpenSSL do not include a validated
556 provider using one of the validated versions listed there. Normally,
558 validated versions alongside F<libcrypto> and F<libssl> compiled from any
H A Dopenssl-glossary.pod91 been validated according to the FIPS 140-2 standard.
/freebsd/crypto/openssl/doc/man3/
H A DX509_verify_cert.pod75 return 1 if a complete chain can be built and validated,
79 If a complete chain can be built and validated both functions return 1.
H A DX509_STORE_CTX_new.pod135 X509_STORE_CTX_set0_verified_chain() sets the validated chain to I<chain>.
171 I<ctx> that contains the validated chain.
177 X509_STORE_CTX_set0_verified_chain() sets the validated chain used
H A DSSL_CTX_dane_enable.pod116 validated certificate chain.
187 DNSSEC-validated TLSA records.
334 That is, they will use DANE authentication when DNSSEC-validated TLSA records
H A DEVP_PKEY_encapsulate.pod55 I<unwrapped> buffer so that its size can be validated by the call, ensuring it
H A DSSL_CTX_set_ct_validation_callback.pod85 validated via DANE-TA(2) or DANE-EE(3) TLSA records which use a private X.509
H A DOCSP_resp_find_status.pod116 signed and that the signer certificate can be validated. It takes I<st> as
/freebsd/crypto/openssl/doc/internal/man3/
H A Dossl_cmp_ctx_set1_caPubs.pod38 which caches any already validated server cert, or NULL if not available.
/freebsd/usr.sbin/bsdconfig/startup/share/
H A Drcvar.subr101 # create the in-memory cache (potentially from validated on-disk cache)
137 # validated on-disk cache. If validation fails, fall-back to
H A Drcconf.subr122 # Create the in-memory cache (potentially from validated on-disk cache)
139 # validated on-disk cache. If validation fails, fall-back to
/freebsd/crypto/openssl/test/
H A Dcmp_vfy_test.c140 X509 *validated = OSSL_CMP_CTX_get0_validatedSrvCert(fixture->cmp_ctx); in execute_validate_msg_test() local
142 return res && (!fixture->expected || TEST_ptr_eq(validated, fixture->cert)); in execute_validate_msg_test()
/freebsd/usr.sbin/bsdconfig/share/packages/
H A Dindex.subr116 # Try to get contents from validated on-disk cache
137 # validated on-disk cache. If validation fails, fall-back to
/freebsd/sys/contrib/device-tree/Bindings/
H A Dwriting-schema.rst202 The DT schema binding documents must be validated using the meta-schema (the
204 binding schema. All of the DT binding documents can be validated using the
/freebsd/contrib/unbound/doc/
H A Dunbound-host.rst76 data) or positive data response validated correctly with one of the
H A DTODO53 of responses over a time interval is collected, and each is validated.
H A Drequirements.txt131 validator failure (SERVFAIL again), when the query is validated later on.
199 doubt. This case is validated by unbound as a 'referral' which
/freebsd/contrib/llvm-project/clang/include/clang/Basic/
H A DDiagnosticSerializationKinds.td133 "module file '%0' was validated as a system module and is now being imported "
/freebsd/sys/contrib/xz-embedded/linux/Documentation/
H A Dxz.txt66 Note that the headers will always have a CRC32 which will be validated
/freebsd/crypto/openssl/doc/man5/
H A Dfips_config.pod216 non-FIPS validated algorithms via broken or mistaken configuration.
/freebsd/contrib/ntp/sntp/
H A DCOPYRIGHT157 validated HTML documents according to the HTML DTD

123