Lines Matching refs:alert
52 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
95 this condition by calling SSL_shutdown() to respond with a close_notify alert in
98 not call SSL_shutdown() in this case, a close_notify alert will not be sent and
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
112 received from the peer, or because a close_notify alert message needs to be sent
119 process is complete (with a close_notify alert having both been sent and
125 peer's close_notify alert is still provided to the application. It also ensures
135 attempt is made to send a close_notify alert, regardless of whether the attempt
137 alert is received, which may occur during any call which processes incoming data
169 close_notify alert was successful or not. This makes the SSL session eligible
176 state without actually sending a close_notify alert message; see
182 received, such that it doesn't need to wait for a close_notify alert, otherwise
188 alert message but simply close the underlying transport (e.g. a TCP connection)
384 For TLS and DTLS, this means that a close_notify alert has been sent but the
398 For TLS and DTLS, this means that a close_notify alert was sent and the peer's
399 close_notify alert was received.
