Home
last modified time | relevance | path

Searched refs:validation (Results 1 – 25 of 140) sorted by relevance

123456

/freebsd/crypto/openssl/doc/man3/
H A DSCT_validate.pod29 The result of the validation checks can be obtained by passing the SCT to
40 Failure to provide the certificate will result in the validation status being
48 (see RFC 6962). If it is required but not provided, the validation status will
55 If the SCT was issued by a log that is not in this CTLOG_STORE, the validation
61 validation status will be SCT_VALIDATION_STATUS_UNKNOWN_VERSION.
64 the time in CT_POLICY_EVAL_CTX), or if it is otherwise invalid, the validation
67 If all checks pass, the validation status will be SCT_VALIDATION_STATUS_VALID.
78 SCT fails validation, or 1 if the SCT passes validation.
81 if any of SCTs fails validation, or 1 if they all pass validation.
83 SCT_get_validation_status() returns the validation status of the SCT.
H A DEVP_PKEY_check.pod8 - key and parameter validation functions
30 implementations may offer a quicker form of validation that omits some checks in
38 implementations may offer a quicker form of validation that omits some checks in
51 Key validation used by the OpenSSL FIPS provider complies with the rules
54 For further information see L<EVP_PKEY-DSA(7)/DSA key validation>,
55 L<EVP_PKEY-DH(7)/DH key validation>, L<EVP_PKEY-EC(7)/EC key validation> and
56 L<EVP_PKEY-RSA(7)/RSA key validation>.
H A DSSL_CTX_set_ct_validation_callback.pod35 This is accomplished by setting a built-in CT validation callback.
55 the validation status of any SCTs.
56 The application can still inspect the validation status of the SCTs at
78 validation will not occur.
109 Certificate Transparency validation cannot be enabled and so a callback cannot
124 validation callback is set, or 0 if no callback (or equivalently a NULL
H A DSCT_print.pod28 SCT_validation_status_string() will return the validation status of an SCT as
30 beforehand in order to set the validation status of an SCT first.
35 the validation status of an B<SCT> object.
H A DCMS_add0_cert.pod26 calling L<CMS_verify(3)> to help chain building in certificate validation.
33 that may be needed for chain building in certificate validation.
39 For signed data, such a CRL may be used in certificate validation
H A DSSL_get0_peer_rpk.pod24 to SSL B<s>'s DANE validation policy.
61 If DANE is not enabled, then no validation will occur.
/freebsd/crypto/openssl/doc/man7/
H A DEVP_PKEY-FFC.pod22 for parameter validation.
24 and I<gindex> may need to be stored for validation purposes.
27 the ASN1 data so they need to be stored externally if validation is required.
75 An optional domain parameter I<seed> value used during generation and validation
77 For validation this needs to set the I<seed> that was produced during generation.
84 then be reused during key validation to verify the value of I<g>. If this value
91 of I<p>. This value must be saved if domain parameter validation is required.
107 These boolean values are used during FIPS186-4 or FIPS186-2 key validation checks
108 (See L<EVP_PKEY_param_check(3)>) to select validation options. By default
115 This boolean value is used during key validation checks
[all …]
H A DEVP_PKEY-DSA.pod10 parameter generation are also required for parameter validation.
12 and I<gindex> may need to be stored for validation purposes. For B<DSA> these
14 validation is required.
17 signature validation, but is still allowed for signature verification.
47 =head2 DSA key validation
51 standard for FFC parameter validation. For backwards compatibility the OpenSSL
52 default provider uses a much simpler check (see below) for parameter validation,
57 also supports validation of legacy "fips186_2" keys.
H A DEVP_RAND-JITTER.pod53 L<ESV|https://csrc.nist.gov/Projects/cryptographic-module-validation-program/entropy-validations>
54 and validation through the
55 L<CMVP|https://csrc.nist.gov/projects/cryptographic-module-validation-program>
H A DEVP_PKEY-DH.pod22 must be used for FIPS186-4. If key validation is required, users should be aware
24 L</DH and DHX key validation>.
73 validation is required.
133 =head2 DH and DHX key validation
137 validation. This means that optional FFC domain parameter values for
139 validation purposes.
242 the actual validation. In production code the return values should be checked.
247 int gindex = ...; /* for the validation */
H A DEVP_RAND-HMAC-DRBG.pod66 L<FIPS 140-3 IG D.R|https://csrc.nist.gov/CSRC/media/Projects/cryptographic-module-validation-progr…
130 L<FIPS 140-3 IG D.R|https://csrc.nist.gov/CSRC/media/Projects/cryptographic-module-validation-progr…
/freebsd/usr.bin/sed/tests/
H A Dregress.P.out5 for validation
6 for validation
H A Dregress.icase1.out3 for validation
H A Dregress.b2a.out2 for validation
H A Dregress.c1.out3 for validation
H A Dregress.G.out5 for validation
H A Dregress.bcb.out3 for validation
H A Dregress.icase2.out3 for validation
H A Dregress.icase3.out3 for validation
H A Dregress.icase4.out3 for validation
H A Dregress.in3 for validation
/freebsd/contrib/llvm-project/llvm/include/llvm/Target/
H A DTargetPfmCounters.td31 // Definition of a validation event. A validation event represents a specific
54 // The name of the event that the validation counter detects.
68 // Processor can list mappings between validation events and real counters
/freebsd/crypto/openssl/include/openssl/
H A Dfipskey.h.in21 * The FIPS validation HMAC key, usable as an array initializer.
27 * The FIPS validation key, as a string.
/freebsd/sys/contrib/openzfs/config/
H A Dkernel-objtool.m429 dnl # 4.6 API for compile-time stack validation
65 [whether compile-time stack validation (objtool) is available])
/freebsd/tests/sys/netpfil/pf/ioctl/
H A DMakefile6 validation

123456