| /freebsd-14.2/crypto/openssl/ |
| H A D | README-FIPS.md | 5 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. 39 If you want to use a validated FIPS provider, but also want to use the latest 94 Download and build a validated FIPS provider 98 which versions are FIPS validated. For this example we use OpenSSL 3.0.0. 122 Note that the OpenSSL 3.1.0 FIPS provider has not been validated
|
| H A D | README-PROVIDERS.md | 59 It is intended that this provider will be FIPS140-2 validated.
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/reset/ |
| H A D | allwinner,sun6i-a31-clock-reset.yaml | 24 # since it's set at the upper level node, and will be validated by
|
| /freebsd-14.2/crypto/openssl/doc/man7/ |
| H A D | OSSL_PROVIDER-FIPS.pod | 11 contains an approved set of cryptographic algorithms that is validated by an 413 Some released versions of OpenSSL do not include a validated 418 provider using one of the validated versions listed there. Normally, 420 validated versions alongside F<libcrypto> and F<libssl> compiled from any
|
| H A D | fips_module.pod | 99 enabled to prevent accidental use of non-FIPS validated algorithms via broken 346 /* Get a FIPS validated digest */ 351 /* Get a non-FIPS validated digest */ 409 properties and the default library context to specify usage of FIPS validated 464 Some released versions of OpenSSL do not include a validated 469 provider using one of the validated versions listed there. Normally, 471 validated versions alongside F<libcrypto> and F<libssl> compiled from any
|
| H A D | openssl-glossary.pod | 91 been validated according to the FIPS 140-2 standard.
|
| /freebsd-14.2/crypto/openssl/doc/man3/ |
| H A D | X509_verify_cert.pod | 67 return 1 if a complete chain can be built and validated, 71 If a complete chain can be built and validated both functions return 1.
|
| H A D | X509_STORE_CTX_new.pod | 109 X509_STORE_CTX_set0_verified_chain() sets the validated chain to I<chain>. 142 I<ctx> that contains the validated chain. 148 X509_STORE_CTX_set0_verified_chain() sets the validated chain used
|
| H A D | EVP_PKEY_encapsulate.pod | 40 the I<unwrapped> buffer so that its size can be validated by the call, ensuring
|
| H A D | SSL_CTX_dane_enable.pod | 116 validated certificate chain. 187 DNSSEC-validated TLSA records. 331 That is, they will use DANE authentication when DNSSEC-validated TLSA records
|
| H A D | SSL_CTX_set_ct_validation_callback.pod | 85 validated via DANE-TA(2) or DANE-EE(3) TLSA records which use a private X.509
|
| H A D | OCSP_resp_find_status.pod | 116 signed and that the signer certificate can be validated. It takes I<st> as
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/clock/ |
| H A D | allwinner,sun4i-a10-mod0-clk.yaml | 24 # since it's set at the upper level node, and will be validated by
|
| /freebsd-14.2/crypto/openssl/doc/internal/man3/ |
| H A D | ossl_cmp_ctx_set1_caPubs.pod | 38 which caches any already validated server cert, or NULL if not available.
|
| /freebsd-14.2/usr.sbin/bsdconfig/startup/share/ |
| H A D | rcvar.subr | 101 # create the in-memory cache (potentially from validated on-disk cache) 137 # validated on-disk cache. If validation fails, fall-back to
|
| H A D | rcconf.subr | 122 # Create the in-memory cache (potentially from validated on-disk cache) 139 # validated on-disk cache. If validation fails, fall-back to
|
| /freebsd-14.2/contrib/googletest/ |
| H A D | .travis.yml | 3 # This file can be validated on:
|
| /freebsd-14.2/sys/contrib/device-tree/Bindings/ |
| H A D | writing-schema.rst | 142 The DT schema binding documents must be validated using the meta-schema (the 144 binding schema. All of the DT binding documents can be validated using the
|
| H A D | example-schema.yaml | 11 # $schema is the meta-schema this schema should be validated with. 248 # Examples are now compiled with dtc and validated against the schemas
|
| /freebsd-14.2/usr.sbin/bsdconfig/share/packages/ |
| H A D | index.subr | 121 # Try to get contents from validated on-disk cache 142 # validated on-disk cache. If validation fails, fall-back to
|
| /freebsd-14.2/crypto/openssl/doc/man5/ |
| H A D | fips_config.pod | 102 non-FIPS validated algorithms via broken or mistaken configuration.
|
| /freebsd-14.2/contrib/llvm-project/clang/include/clang/Basic/ |
| H A D | DiagnosticSerializationKinds.td | 128 "module file '%0' was validated as a system module and is now being imported "
|
| /freebsd-14.2/contrib/unbound/doc/ |
| H A D | TODO | 53 of responses over a time interval is collected, and each is validated.
|
| H A D | requirements.txt | 131 validator failure (SERVFAIL again), when the query is validated later on. 199 doubt. This case is validated by unbound as a 'referral' which
|
| /freebsd-14.2/sys/contrib/xz-embedded/linux/Documentation/ |
| H A D | xz.txt | 66 Note that the headers will always have a CRC32 which will be validated
|