Home
last modified time | relevance | path

Searched full:verification (Results 1 – 25 of 855) sorted by relevance

12345678910>>...35

/freebsd-14-stable/crypto/openssl/doc/man3/
HDSSL_CTX_set_cert_verify_callback.pod5 SSL_CTX_set_cert_verify_callback - set peer certificate verification procedure
17 SSL_CTX_set_cert_verify_callback() sets the verification callback function for
24 a verification function is called regardless of the verification mode.
25 If the application does not explicitly specify a verification callback function,
26 the built-in verification function is used.
27 If a verification callback I<callback> is specified via
33 I<callback> should return 1 to indicate verification success
34 and 0 to indicate verification failure.
38 if the verification mode is B<SSL_VERIFY_NONE>.
45 typically done in case the certificate verification was not yet able
[all …]
HDSSL_CTX_set_verify.pod12 - set various SSL/TLS parameters for peer certificate verification
33 SSL_CTX_set_verify() sets the verification flags for B<ctx> to be B<mode> and
37 SSL_set_verify() sets the verification flags for B<ssl> to be B<mode> and
45 of the current SSL object that is doing the verification.
50 This would be typically done in case the certificate verification was not yet
55 information needed for the verification.
57 server certificate verification step.
63 verification that shall be allowed for B<ctx>.
66 verification that shall be allowed for B<ssl>.
81 The verification of certificates can be controlled by a set of logically
[all …]
HDX509_STORE_CTX_new.pod77 X509_STORE_CTX_init() sets up I<ctx> for a subsequent verification operation.
80 given I<ctx>. Among others, it sets the verification parameters associcated
84 L<X509_STORE_CTX_verify(3)>, i.e., a context is only good for one verification.
95 will need a verification target.
98 list of untrusted certificates as its verification target,
117 verification to I<sk>. These CRLs will only be used if CRL verification is
123 to the verification parameters associated with I<ctx>.
125 X509_STORE_CTX_set0_param() sets the internal verification parameter pointer
145 L<openssl-verification-options(1)/Certification Path Building> and
146 L<openssl-verification-options(1)/Certification Path Validation>.
[all …]
HDX509_STORE_CTX_set_verify_cb.pod19 - get and set X509_STORE_CTX components such as verification callback
46 X509_STORE_CTX_set_verify_cb() sets the verification callback of B<ctx> to
49 The verification callback can be used to customise the operation of certificate
50 verification, for instance by overriding error conditions or logging errors for
53 However, a verification callback is B<not> essential and the default operation
63 is performing the verification operation. A callback can examine this
68 X509_STORE_CTX_print_verify_cb() is a verification callback function that,
69 when a certificate verification has failed, adds an entry to the error queue
89 In general a verification callback should B<NOT> unconditionally return 1 in
90 all circumstances because this will allow verification to succeed no matter
[all …]
HDX509_VERIFY_PARAM_set_flags.pod21 - X509 verification parameters
75 a certificate verification operation.
78 it with B<flags>. See L</VERIFICATION FLAGS> for a complete
84 which specifies how verification flags are copied from one structure to
90 X509_VERIFY_PARAM_set_purpose() sets the verification purpose in B<param>
98 X509_VERIFY_PARAM_set_time() sets the verification time in B<param> to
110 X509_VERIFY_PARAM_set_depth() sets the maximum verification depth to B<depth>.
151 certificate verification automatically invokes L<X509_check_host(3)>
157 be suppressed as appropriate when DANE verification is enabled.
197 is specified, certificate verification automatically invokes
[all …]
HDSSL_get_verify_result.pod5 SSL_get_verify_result - get result of peer certificate verification
15 SSL_get_verify_result() returns the result of the verification of the
20 SSL_get_verify_result() can only return one error code while the verification
22 the last verification error that occurred during the processing is available
25 Sometimes there can be a sequence of errors leading to the verification
32 The verification result is part of the established session and is restored
38 X509_V_OK. This is because no verification error occurred, it does however
50 The verification succeeded or no peer certificate was presented.
HDX509_STORE_CTX_get_error.pod9 X509_verify_cert_error_string - get or set certificate verification status
30 These functions are typically called after certificate or chain verification
32 an error or in a verification callback to determine the nature of an error.
37 an error, likely because a verification callback function has waived the error.
40 it might be used in a verification callback to set an error based on additional
61 It may be examined by a verification callback invoked to handle each error
62 encountered during chain verification and is no longer required after such a
73 verification is successful. Otherwise the returned chain may be incomplete or
80 verification error I<n>.
92 verification error I<n>.
[all …]
HDSSL_CTX_get_verify_mode.pod5 …h, SSL_get_verify_callback, SSL_CTX_get_verify_callback - get currently set verification parameters
20 SSL_CTX_get_verify_mode() returns the verification mode currently set in
23 SSL_get_verify_mode() returns the verification mode currently set in
26 SSL_CTX_get_verify_depth() returns the verification depth limit currently set
30 SSL_get_verify_depth() returns the verification depth limit currently set
34 SSL_CTX_get_verify_callback() returns a function pointer to the verification
38 SSL_get_verify_callback() returns a function pointer to the verification
HDSSL_set_retry_verify.pod5 SSL_set_retry_verify - indicate that certificate verification should be retried
15 SSL_set_retry_verify() should be called from the certificate verification
19 is resumed again by the application, retrying the verification step.
26 verification callback on the client side is undefined.
45 if (/* we need to retry verification callback */)
48 /* do normal processing of the verification callback */
58 incompatible handling of a negative return value from the verification
HDSSL_CTX_set1_verify_cert_store.pod11 verification or chain store
34 set the certificate store used for certificate verification to B<st>.
60 The verification store is used to verify the certificate chain sent by the
61 peer: that is an SSL/TLS client will use the verification store to verify
67 L<openssl-verification-options(1)/Certification Path Building> and
68 L<openssl-verification-options(1)/Certification Path Validation>.
79 If the chain or the verification store is not set then the store associated
HDSSL_CTX_set_ct_validation_callback.pod41 TLS handshake with the verification mode set to B<SSL_VERIFY_PEER>, if the peer
43 If the verification mode is B<SSL_VERIFY_NONE>, the handshake will continue
45 However, in that case if the verification status before the built-in callback
49 handshake completion, even after session resumption since the verification
54 handshake continues, and the verification status is not modified, regardless of
69 The TLS handshake is aborted if the verification mode is not B<SSL_VERIFY_NONE>
88 nor to have specified server verification via DANE-TA(2) or DANE-EE(3) TLSA
HDX509_verify_cert.pod37 The verification context, of type B<X509_STORE_CTX>, can be constructed
43 such as a callback function that allows customizing the verification outcome.
44 A complete description of the certificate verification process is contained in
45 the L<openssl-verification-options(1)> manual page.
78 verification indicated success, the stored error code may be different from
79 X509_V_OK, likely because a verification callback function has waived the error.
HDSSL_CTX_get0_param.pod7 get and set verification parameters
27 the verification parameters for B<ctx> or B<ssl> respectively. The returned
30 SSL_CTX_set1_param() and SSL_set1_param() set the verification parameters
34 set the purpose parameter on the verification parameters object. These functions
38 which set the trust parameter on the verification parameters object. These
HDSSL_set_verify_result.pod5 SSL_set_verify_result - override result of peer certificate verification
16 result of the verification of the X509 certificate presented by the peer,
21 SSL_set_verify_result() overrides the verification result. It only changes
22 the verification result of the B<ssl> object. It does not become part of the
/freebsd-14-stable/crypto/heimdal/doc/doxyout/hx509/man/man3/
HDhx509_verify.31 .TH "hx509 verification functions" 3 "11 Jan 2012" "Version 1.5.2" "Heimdalx509library" \" -*- nrof…
5 hx509 verification functions \-
192 … the verification context, makes an reference to the keyset, so the consumer can free the keyset i…
196 \fIctx\fP a verification context
204 …estruction of the verification context. If there is no revoke context, the verification process is…
208 \fIctx\fP a verification context.
216 Free an hx509 verification context.
226 Allocate an verification context that is used fo control the verification process.
249 \fIctx\fP A hx509 verification context.
268 \fIctx\fP a verification context
[all …]
/freebsd-14-stable/secure/lib/libcrypto/man/man3/
HDSSL_CTX_set_verify.3149 \&\- set various SSL/TLS parameters for peer certificate verification
170 \&\fBSSL_CTX_set_verify()\fR sets the verification flags for \fBctx\fR to be \fBmode\fR and
174 \&\fBSSL_set_verify()\fR sets the verification flags for \fBssl\fR to be \fBmode\fR and
182 of the current \s-1SSL\s0 object that is doing the verification.
187 This would be typically done in case the certificate verification was not yet
192 information needed for the verification.
194 server certificate verification step.
200 verification that shall be allowed for \fBctx\fR.
203 verification that shall be allowed for \fBssl\fR.
217 The verification of certificates can be controlled by a set of logically
[all …]
HDSSL_CTX_set_cert_verify_callback.3142 SSL_CTX_set_cert_verify_callback \- set peer certificate verification procedure
154 \&\fBSSL_CTX_set_cert_verify_callback()\fR sets the verification callback function for
160 a verification function is called regardless of the verification mode.
161 If the application does not explicitly specify a verification callback function,
162 the built-in verification function is used.
163 If a verification callback \fIcallback\fR is specified via
169 \&\fIcallback\fR should return 1 to indicate verification success
170 and 0 to indicate verification failure.
174 if the verification mode is \fB\s-1SSL_VERIFY_NONE\s0\fR.
181 typically done in case the certificate verification was not yet able
[all …]
HDX509_VERIFY_PARAM_set_flags.3158 \&\- X509 verification parameters
212 a certificate verification operation.
215 it with \fBflags\fR. See \*(L"\s-1VERIFICATION FLAGS\*(R"\s0 for a complete
221 which specifies how verification flags are copied from one structure to
227 \&\fBX509_VERIFY_PARAM_set_purpose()\fR sets the verification purpose in \fBparam\fR
235 \&\fBX509_VERIFY_PARAM_set_time()\fR sets the verification time in \fBparam\fR to
247 \&\fBX509_VERIFY_PARAM_set_depth()\fR sets the maximum verification depth to \fBdepth\fR.
288 certificate verification automatically invokes \fBX509_check_host\fR\|(3)
294 be suppressed as appropriate when \s-1DANE\s0 verification is enabled.
334 is specified, certificate verification automatically invokes
[all …]
HDX509_STORE_CTX_get_error.3146 X509_verify_cert_error_string \- get or set certificate verification status
167 These functions are typically called after certificate or chain verification
169 an error or in a verification callback to determine the nature of an error.
174 an error, likely because a verification callback function has waived the error.
177 it might be used in a verification callback to set an error based on additional
198 It may be examined by a verification callback invoked to handle each error
199 encountered during chain verification and is no longer required after such a
210 verification is successful. Otherwise the returned chain may be incomplete or
219 verification error \fIn\fR.
230 verification error \fIn\fR.
[all …]
HDX509_STORE_CTX_set_verify_cb.3156 \&\- get and set X509_STORE_CTX components such as verification callback
183 \&\fBX509_STORE_CTX_set_verify_cb()\fR sets the verification callback of \fBctx\fR to
186 The verification callback can be used to customise the operation of certificate
187 verification, for instance by overriding error conditions or logging errors for
190 However, a verification callback is \fBnot\fR essential and the default operation
200 is performing the verification operation. A callback can examine this
205 \&\fBX509_STORE_CTX_print_verify_cb()\fR is a verification callback function that,
206 when a certificate verification has failed, adds an entry to the error queue
224 In general a verification callback should \fB\s-1NOT\s0\fR unconditionally return 1 in
225 all circumstances because this will allow verification to succeed no matter
[all …]
HDX509_STORE_CTX_new.3215 \&\fBX509_STORE_CTX_verify\fR\|(3), i.e., a context is only good for one verification.
226 will need a verification target.
229 list of untrusted certificates as its verification target,
248 verification to \fIsk\fR. These CRLs will only be used if \s-1CRL\s0 verification is
254 to the verification parameters associated with \fIctx\fR.
256 \&\fBX509_STORE_CTX_set0_param()\fR sets the internal verification parameter pointer
276 \&\*(L"Certification Path Building\*(R" in \fBopenssl\-verification\-options\fR\|(1) and
277 \&\*(L"Certification Path Validation\*(R" in \fBopenssl\-verification\-options\fR\|(1).
284 \&\fBX509_STORE_CTX_set_default()\fR looks up and sets the default verification
320 custom \*(L"purpose\*(R" (see below) or supply a nondefault verification callback
[all …]
HDSSL_get_verify_result.3142 SSL_get_verify_result \- get result of peer certificate verification
152 \&\fBSSL_get_verify_result()\fR returns the result of the verification of the
156 \&\fBSSL_get_verify_result()\fR can only return one error code while the verification
158 the last verification error that occurred during the processing is available
161 Sometimes there can be a sequence of errors leading to the verification
168 The verification result is part of the established session and is restored
173 X509_V_OK. This is because no verification error occurred, it does however
181 The verification succeeded or no peer certificate was presented.
HDSSL_set_retry_verify.3142 SSL_set_retry_verify \- indicate that certificate verification should be retried
152 \&\fBSSL_set_retry_verify()\fR should be called from the certificate verification
156 is resumed again by the application, retrying the verification step.
162 verification callback on the client side is undefined.
180 \& if (/* we need to retry verification callback */)
183 \& /* do normal processing of the verification callback */
192 incompatible handling of a negative return value from the verification
HDSSL_CTX_get_verify_mode.3142 …, SSL_get_verify_callback, SSL_CTX_get_verify_callback \- get currently set verification parameters
157 \&\fBSSL_CTX_get_verify_mode()\fR returns the verification mode currently set in
160 \&\fBSSL_get_verify_mode()\fR returns the verification mode currently set in
163 \&\fBSSL_CTX_get_verify_depth()\fR returns the verification depth limit currently set
167 \&\fBSSL_get_verify_depth()\fR returns the verification depth limit currently set
171 \&\fBSSL_CTX_get_verify_callback()\fR returns a function pointer to the verification
175 \&\fBSSL_get_verify_callback()\fR returns a function pointer to the verification
/freebsd-14-stable/contrib/libfido2/man/
HDfido2-token.1174 A PIN or equivalent user-verification gesture is required.
191 A PIN or equivalent user-verification gesture is required.
203 .Dq user verification always
218 A PIN or equivalent user-verification gesture is required.
237 A PIN or equivalent user-verification gesture is required.
264 A PIN or equivalent user-verification gesture is required.
304 A PIN or equivalent user-verification gesture is required.
323 A PIN or equivalent user-verification gesture is required.
342 A PIN or equivalent user-verification gesture is required.
378 .Dq user verification always
[all …]

12345678910>>...35