| /openssl/doc/man3/ |
| H A D | SSL_alert_type_string.pod | 58 =item "F"/"fatal"
85 MAC. This message is always fatal.
91 fatal.
129 other fields. This is always fatal.
148 message is always fatal.
154 This message is always fatal.
160 message is always fatal.
173 message is always fatal.
180 always fatal.
187 fatal.
[all …]
|
| H A D | DTLSv1_listen.pod | 120 A return value of 0 indicates a non-fatal error. This could (for
124 call to DTLSv1_listen() in the event of a non-fatal error.
126 A return value of <0 indicates a fatal error. This could (for example) be
129 For DTLSv1_listen(), prior to OpenSSL 1.1.0, fatal and non-fatal errors both
131 errors as non-fatal), whilst return codes >0 indicate success.
|
| H A D | ERR_GET_LIB.pod | 24 ERR_FATAL_ERROR() indicates whether a given error code is a fatal error.
42 is fatal, respectively.
|
| H A D | CONF_modules_load_file.pod | 51 considered fatal and no further modules are loaded.
82 consider a configuration file error as fatal and exit immediately.
97 considered fatal):
|
| H A D | SSL_extension_supported.pod | 119 If B<add_cb> returns -1 a fatal handshake error occurs using the TLS
164 1. If it returns 0 or a negative value a fatal handshake error occurs
259 If the same custom extension type is received multiple times a fatal
262 the ClientHello a fatal B<unsupported_extension> alert is sent and the
|
| H A D | PKCS12_create.pod | 87 a fatal error is returned.
100 If I<cb> is specified, then it should return 1 for success and -1 for a fatal error.
|
| H A D | SSL_set_shutdown.pod | 39 or a fatal error.
|
| H A D | SSL_do_handshake.pod | 58 The TLS/SSL handshake was not successful because a fatal error occurred either
|
| H A D | SSL_accept.pod | 57 The TLS/SSL handshake was not successful because a fatal error occurred either
|
| H A D | ASN1_EXTERN_FUNCS.pod | 128 The return value should be negative if a fatal error occurred, or 0 if a
129 non-fatal error occurred. Otherwise it should return the length of the encoded
|
| H A D | X509V3_get_d2i.pod | 219 and 0 if it fails due to a non-fatal error (extension not found, already exists,
220 cannot be encoded) or -1 due to a fatal error such as a memory allocation
|
| H A D | SSL_CTX_set_session_id_context.pod | 51 will not be reused but a fatal error will be flagged and the handshake
|
| H A D | SSL_CTX_set_cert_cb.pod | 27 fatal internal error alert. A negative return value will suspend the handshake
|
| H A D | SSL_CTX_set_alpn_select_cb.pod | 97 fatal to the connection if this callback returns a value other than
192 B<SSL_TLSEXT_ERR_OK> if successful. Any other value is fatal to the connection.
|
| H A D | SSL_connect.pod | 72 The TLS/SSL handshake was not successful, because a fatal error occurred either
|
| H A D | SSL_get_error.pod | 167 Some non-recoverable, fatal I/O error occurred. The OpenSSL error queue may
177 A non-recoverable, fatal error in the SSL library occurred, usually a protocol
|
| H A D | d2i_RSAPrivateKey.pod | 234 /* fatal error handling */
238 /* non-fatal error handling */
|
| /openssl/doc/man7/ |
| H A D | ossl-guide-tls-client-non-block.pod | 38 currently unable to read or write will return immediately with a non-fatal
137 L<SSL_write_ex(3)>. Errors may be fatal (for example because the underlying
138 connection has failed), or non-fatal (for example because we are trying to read
146 out what type of error has occurred. If the error is non-fatal and can be
209 the event of a non-fatal failure, it waits until a retry of the I/O operation
211 in the previous section). It returns 1 in the event of a non-fatal error
212 (except EOF), 0 in the event of EOF, or -1 if a fatal error occurred.
225 socket it is very likely that calls to this function will fail with a non-fatal
241 this stage, so such a response is treated in the same way as a fatal error.
280 same way as a fatal error.
[all …]
|
| H A D | ossl-guide-quic-client-non-block.pod | 42 L<SSL_read_ex(3)> or L<SSL_write_ex(3)> will return immediately with a non-fatal
171 has failed), or non-fatal (for example because we are trying to read from the
179 out what type of error has occurred. If the error is non-fatal and can be
225 * Some stream fatal error occurred. This could be because of a
263 the event of a non-fatal failure, it waits until a retry of the I/O operation
265 in the previous section). It returns 1 in the event of a non-fatal error
266 (except EOF), 0 in the event of EOF, or -1 if a fatal error occurred.
329 this stage, so such a response is treated in the same way as a fatal error.
335 a nonblocking B<SSL> object, this call could fail with a non-fatal error. In
368 same way as a fatal error.
[all …]
|
| H A D | ossl-guide-quic-client-block.pod | 250 fatal for that stream), but the underlying connection itself may still be
285 * Some stream fatal error occurred. This could be because of a stream
312 fatal error. We can use L<SSL_get_stream_read_state(3)> to determine whether the
313 stream has been reset, or if some other fatal error has occurred.
|
| /openssl/apps/lib/ |
| H A D | http_server.c | 286 goto fatal; in http_server_get_asn1_req()
394 goto fatal; in http_server_get_asn1_req()
477 goto fatal; in http_server_get_asn1_req()
491 fatal: in http_server_get_asn1_req()
|
| /openssl/ssl/ |
| H A D | t1_enc.c | 32 unsigned char *out, size_t olen, int fatal) in tls1_PRF() argument
42 if (fatal) in tls1_PRF()
80 if (fatal) in tls1_PRF()
|
| H A D | ssl_sess.c | 589 int fatal = 0; in ssl_get_prev_session() local
613 fatal = 1; in ssl_get_prev_session()
662 fatal = 1; in ssl_get_prev_session()
680 fatal = 1; in ssl_get_prev_session()
713 if (fatal) in ssl_get_prev_session()
|
| H A D | tls13_enc.c | 103 unsigned char *out, size_t outlen, int fatal) in tls13_hkdf_expand() argument
110 out, outlen, !fatal); in tls13_hkdf_expand()
111 if (ret == 0 && fatal) in tls13_hkdf_expand()
|
| /openssl/include/openssl/ |
| H A D | ssl.h.in | 1156 /* fatal */
1158 /* fatal */
1162 /* fatal */
1164 /* fatal */
1173 /* fatal */
1175 /* fatal */
1177 /* fatal */
1179 /* fatal */
1182 /* fatal */
1184 /* fatal */
[all …]
|
