Home
last modified time | relevance | path

Searched refs:alert (Results 1 – 25 of 49) sorted by relevance

12

/openssl/doc/man3/
H A DSSL_alert_type_string.pod20 type of the alert specified by B<value>.
26 describing the reason of the alert specified by B<value>.
29 of the alert specified by B<value>.
34 a special situation, it sends an alert. The alert is sent as a special message
39 "close notify" alert is sent as a warning alert. Other examples for
44 alert on it discretion.
46 Several alert messages must be sent as fatal alert messages as specified
62 This indicates that no support is available for this alert type.
63 Probably B<value> does not contain a correct alert message.
74 The connection shall be closed. This is a warning alert.
[all …]
H A DSSL_shutdown.pod52 close_notify alert message. The shutdown process for SSL/TLS and DTLS
59 A close_notify shutdown alert message is sent to the peer.
63 A close_notify shutdown alert message is received from the peer.
73 process and causes OpenSSL to try to send a close_notify shutdown alert to the
75 responds in turn with a close_notify shutdown alert message.
90 close_notify alert message, an application will be notified of this as an EOF
105 close_notify alert message is written to the peer (returning 0), and upon a
111 complete (for example, because a close_notify alert message has not yet been
119 process is complete (with a close_notify alert having both been sent and
176 state without actually sending a close_notify alert message; see
[all …]
H A DSSL_set_shutdown.pod33 A close_notify shutdown alert was sent to the peer, the connection is being
38 A shutdown alert was received form the peer, either a normal close_notify
51 alert but to not wait for the peer's answer, when the underlying connection
54 close alert to the peer (see L<SSL_shutdown(3)>).
H A DSSL_CTX_set_info_callback.pod49 an alert appears, or an error occurs.
54 If an alert is handled, SSL_CB_ALERT is set and B<ret> specifies the alert
83 Callback has been called due to an alert being sent or received.
142 BIO_printf(bio_err, "SSL3 alert %s:%s:%s\n", str,
H A DSSL_CTX_set_quiet_shutdown.pod40 close_notify alert messages using L<SSL_shutdown(3)>
48 The session is thus considered to be shutdown, but no close_notify alert
H A DSSL_CTX_set_tlsext_servername_callback.pod47 handshake will be aborted. The value of the alert to be used should be stored in
54 However, the handshake will continue and send a warning alert instead. The value
55 of the alert should be stored in the location pointed to by the B<al> parameter
H A DSSL_CTX_set_verify.pod102 immediately terminated with an alert message containing the reason for
110 immediately terminated with an alert message containing the reason for
117 handshake is immediately terminated with a "handshake failure" alert.
193 SSL_VERIFY_PEER is set, a verification failure alert is sent to the peer and
205 alert message, if SSL_VERIFY_PEER is set.
H A DSSL_CTX_set_options.pod214 Some TLS implementations do not send the mandatory close_notify alert on
215 shutdown. If the application tries to wait for the close_notify alert but the
217 option is enabled the peer does not need to send the close_notify alert and a
218 closed connection will be treated as if the close_notify alert was received.
427 server with a B<no_renegotiation> warning alert if TLS v1.0 is used or a fatal
428 B<handshake_failure> alert in SSL v3.0.
431 B<handshake_failure> alert is sent. This is because the server code may be
H A DSSL_extension_supported.pod120 alert value specified in B<*al>.
165 using the TLS alert value specified in B<*al>.
260 B<decode_error> alert is sent and the handshake aborts. If a custom extension
262 the ClientHello a fatal B<unsupported_extension> alert is sent and the
/openssl/test/recipes/
H A D70-test_tls13alerts.t41 my $alert = TLSProxy::Message->alert();
42 ok(TLSProxy::Message->fail() && !$alert->server() && !$alert->encrypted(), "Client sends an unencry…
H A D70-test_tls13downgrade.t70 my $alert = TLSProxy::Message->alert();
72 && !$alert->server()
73 && $alert->description() == TLSProxy::Message::AL_DESC_ILLEGAL_PARAMETER,
H A D70-test_sslrecords.t458 my $alert = pack('CC', TLSProxy::Message::AL_LEVEL_FATAL,
460 my $alertlen = length $alert;
469 $alert,
470 $alert
H A D70-test_comp.t177 return 1 if TLSProxy::Message->alert->description() == $alert_type;
/openssl/test/ssl-tests/
H A D09-alpn.cnf8 test-3 = 3-alpn-alert-on-mismatch
118 [3-alpn-alert-on-mismatch]
119 ssl_conf = 3-alpn-alert-on-mismatch-ssl
121 [3-alpn-alert-on-mismatch-ssl]
122 server = 3-alpn-alert-on-mismatch-server
123 client = 3-alpn-alert-on-mismatch-client
125 [3-alpn-alert-on-mismatch-server]
130 [3-alpn-alert-on-mismatch-client]
141 [3-alpn-alert-on-mismatch-server-extra]
144 [3-alpn-alert-on-mismatch-client-extra]
[all …]
H A D09-alpn.cnf.in68 name => "alpn-alert-on-mismatch",
264 name => "alpn-alert-on-mismatch-resumption",
/openssl/ssl/quic/
H A Dquic_tls.c17 if ((rl) != NULL) (rl)->alert = (ad); \
74 int alert; member
246 unsigned char alert; in quic_write_records() local
301 alert = template->buf[1]; in quic_write_records()
303 if (!rl->qtls->args.alert_cb(rl->qtls->args.alert_cb_arg, alert)) { in quic_write_records()
443 return rl->alert; in quic_get_alert_code()
/openssl/util/perl/TLSProxy/
H A DMessage.pm160 my $alert;
173 $alert = undef;
326 $alert = TLSProxy::Alert->new(
517 sub alert subroutine
519 return $alert;
/openssl/ssl/record/
H A Drec_layer_d1.c384 PACKET alert; in dtls1_read_bytes() local
386 if (!PACKET_buf_init(&alert, alert_bytes, rr->length) in dtls1_read_bytes()
387 || !PACKET_get_1(&alert, &alert_level) in dtls1_read_bytes()
388 || !PACKET_get_1(&alert, &alert_descr) in dtls1_read_bytes()
389 || PACKET_remaining(&alert) != 0) { in dtls1_read_bytes()
/openssl/test/
H A DREADME.ssltest.md69 * ExpectedClientAlert, ExpectedServerAlert - expected alert. See
70 `test/helpers/ssl_test_ctx.c` for known values. Note: the expected alert is currently
71 matched against the _last_ received alert (i.e., a fatal alert or a
72 `close_notify`). Warning alert expectations are not yet supported. (A warning
73 alert will not be correctly matched, if followed by a `close_notify` or
74 another alert.)
H A Dssl_test.c29 static const char *print_alert(int alert) in print_alert() argument
31 return alert ? SSL_alert_desc_string_long(alert) : "no alert"; in print_alert()
/openssl/crypto/err/
H A Dopenssl.txt1446 SSL_R_INVALID_ALERT:205:invalid alert
1585 SSL_R_SSLV3_ALERT_BAD_RECORD_MAC:1020:ssl/tls alert bad record mac
1595 ssl/tls alert unsupported certificate
1618 SSL_R_TLSV1_ALERT_ACCESS_DENIED:1049:tlsv1 alert access denied
1619 SSL_R_TLSV1_ALERT_DECODE_ERROR:1050:tlsv1 alert decode error
1621 SSL_R_TLSV1_ALERT_DECRYPT_ERROR:1051:tlsv1 alert decrypt error
1625 SSL_R_TLSV1_ALERT_INTERNAL_ERROR:1080:tlsv1 alert internal error
1627 tlsv1 alert no application protocol
1631 SSL_R_TLSV1_ALERT_UNKNOWN_CA:1048:tlsv1 alert unknown ca
1633 SSL_R_TLSV1_ALERT_USER_CANCELLED:1090:tlsv1 alert user cancelled
[all …]
/openssl/doc/designs/quic-design/
H A Dquic-tls.md129 In the event that an error occurs a normal TLS handshake would send a TLS alert
131 attempts to send an alert and will communicate this via the `alert_cb` callback.
197 alert. This manifests itself as a call to `write_records` indicating a type of
199 alert data supplied by the TLS implementation (always a 2 byte record payload)
200 and pull out the alert description (a one byte integer) and invoke the
202 alert record to be fragmented across two 1 byte records this is never done in
204 the optimising assumption that both bytes of an alert are always sent together.
/openssl/test/helpers/
H A Dssl_test_ctx.c129 __owur static int parse_alert(int *alert, const char *value) in parse_alert() argument
131 return parse_enum(ssl_alerts, OSSL_NELEM(ssl_alerts), alert, value); in parse_alert()
144 const char *ssl_alert_name(int alert) in ssl_alert_name() argument
146 return enum_name(ssl_alerts, OSSL_NELEM(ssl_alerts), alert); in ssl_alert_name()
H A Dssl_test_ctx.h240 const char *ssl_alert_name(int alert);
/openssl/ssl/record/methods/
H A Ddtls_meth.c200 if (rl->alert != SSL_AD_NO_ALERT) { in dtls_process_record()
499 if (rl->alert != SSL_AD_NO_ALERT) { in dtls_get_more_records()
560 if (rl->alert != SSL_AD_NO_ALERT) { in dtls_get_more_records()

Completed in 55 milliseconds

12