Home
last modified time | relevance | path

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

12345678910>>...25

/netbsd-src/crypto/external/bsd/openssl/dist/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.pod24 calling L<CMS_verify(3)> to help chain building in certificate validation.
28 that may be needed for chain building in certificate validation.
34 For signed data, such a CRL may be used in certificate validation
/netbsd-src/crypto/external/bsd/openssl.old/dist/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 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.
/netbsd-src/crypto/external/bsd/netpgp/dist/src/lib/
H A Dvalidate.c795 validate_data_cb_t validation; in pgp_validate_file() local
833 (void) memset(&validation, 0x0, sizeof(validation)); in pgp_validate_file()
834 infd = pgp_setup_file_read(io, &parse, signame, &validation, in pgp_validate_file()
841 validation.detachname = netpgp_strdup(dataname); in pgp_validate_file()
845 validation.result = result; in pgp_validate_file()
846 validation.keyring = keyring; in pgp_validate_file()
847 validation.mem = pgp_memory_new(); in pgp_validate_file()
848 pgp_memory_init(validation.mem, 128); in pgp_validate_file()
851 validation.reader = parse->readinfo.arg; in pgp_validate_file()
886 len = (unsigned)pgp_mem_len(validation.mem); in pgp_validate_file()
[all …]
/netbsd-src/crypto/external/bsd/openssl/dist/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.
32 =head2 DSA key validation
36 standard for FFC parameter validation. For backwards compatibility the OpenSSL
37 default provider uses a much simpler check (see below) for parameter validation,
42 also supports validation of legacy "fips186_2" keys.
/netbsd-src/external/bsd/unbound/dist/libunbound/python/doc/
H A Dintro.rst8 DNSSEC validation.
14 The library also performs public-key validation of results with DNSSEC.
26 There are two main classes :class:`unbound.ub_ctx` (a validation and resolution
27 context) and :class:`unbound.ub_result` which contains the validation and
38 * Customizable caching validation resolver for synchronous and asynchronous
55 * Applications where the validation of DNS records is required
/netbsd-src/external/mpl/bind/dist/doc/dnssec-guide/
H A Dvalidation.rst24 resolver. A validating resolver performs validation for each remote
34 So how do we turn on DNSSEC validation? It turns out that you may not need
36 including packages and distributions - have shipped with DNSSEC validation
38 whether you already have DNSSEC validation enabled by following the steps
42 validation must be explicitly enabled. To do this, you only need to
49 dnssec-validation auto;
64 Once DNSSEC validation is enabled, any DNS response that does not pass
65 the validation checks results in a failure to resolve the domain name
78 could cause all validation for ``.org`` domains to fail. To end
81 be tempted to disable validation; ther
413 how_does_dnssec_change_dns_lookup_revisited:any:`dnssec-validation` global() argument
[all...]
H A Dtroubleshooting.rst103 validation. You can use the :option:`dig +cd` flag to disable
104 validation, as described in
107 When there is indeed a DNSSEC validation problem, the visible symptoms,
108 unfortunately, are very limited. With DNSSEC validation enabled, if a
151 DNSSEC validation error messages show up in :any:`syslog` as a
162 to get more details about why DNSSEC validation may have
180 validation messages) in BIND 9 and have it sent to :any:`syslog`:
214 validating ./NS: attempting positive response validation
216 validating ./DNSKEY: attempting positive response validation
225 validating ftp.isc.org/A: attempting positive response validation
[all...]
/netbsd-src/external/mpl/bind/dist/
H A Dbind.keys18 # To use the built-in root key, set "dnssec-validation auto;" in the
19 # named.conf options, or else leave "dnssec-validation" unset. If
20 # "dnssec-validation" is set to "yes", then the keys in this file are
22 # validation to work. "auto" is the default setting, unless named is
23 # built with "configure --disable-auto-validation", in which case the
/netbsd-src/external/apache2/llvm/dist/llvm/bindings/ocaml/analysis/
H A Dllvm_analysis.mli16 human-readable validation report. See [llvm::verifyModule]. *)
24 validation report to [stderr] and aborts the program if it is invalid. See
30 validation report to [stderr] and aborts the program if it is invalid. See
/netbsd-src/crypto/external/bsd/openssl/dist/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.
/netbsd-src/external/mpl/bind/dist/bin/tests/system/dnssec/ns4/
H A Dnamed1.conf.in25 dnssec-validation yes;
37 # But since dnssec-validation is set to "yes" not "auto", that
/netbsd-src/external/mpl/bind/dist/doc/notes/
H A Dnotes-9.18.14.rst
/netbsd-src/external/apache2/llvm/dist/llvm/docs/AMDGPU/
H A Dgfx10_msg.rst83 // sendmsg with strict arguments validation
91 // sendmsg with validation of value range only
H A Dgfx9_msg.rst83 // sendmsg with strict arguments validation
91 // sendmsg with validation of value range only
H A Dgfx8_msg.rst81 // sendmsg with strict arguments validation
88 // sendmsg with validation of value range only
H A Dgfx90a_msg.rst83 // sendmsg with strict arguments validation
91 // sendmsg with validation of value range only
H A Dgfx7_msg.rst81 // sendmsg with strict arguments validation
88 // sendmsg with validation of value range only
/netbsd-src/external/apache2/llvm/dist/llvm/docs/
H A DStackSafetyAnalysis.rst49 bugs in instrumented code. To avoid that we want additional validation tool.
51 AddressSanitizer may help with this validation. We can instrument all variables

12345678910>>...25