Lines Matching full:alert

110 close_notify alert message. The shutdown process for SSL/TLS and DTLS
113 A close_notify shutdown alert message is sent to the peer.
115 A close_notify shutdown alert message is received from the peer.
122 process and causes OpenSSL to try to send a close_notify shutdown alert to the
124 responds in turn with a close_notify shutdown alert message.
138 close_notify alert message, an application will be notified of this as an EOF
143 this condition by calling \fBSSL_shutdown()\fR to respond with a close_notify alert in
146 not call \fBSSL_shutdown()\fR in this case, a close_notify alert will not be sent and
152 close_notify alert message is written to the peer (returning 0), and upon a
158 complete (for example, because a close_notify alert message has not yet been
159 received from the peer, or because a close_notify alert message needs to be sent
166 process is complete (with a close_notify alert having both been sent and
172 peer's close_notify alert is still provided to the application. It also ensures
182 attempt is made to send a close_notify alert, regardless of whether the attempt
184 alert is received, which may occur during any call which processes incoming data
214 close_notify alert was successful or not. This makes the SSL session eligible
220 state without actually sending a close_notify alert message; see
226 received, such that it doesn't need to wait for a close_notify alert, otherwise
231 alert message but simply close the underlying transport (e.g. a TCP connection)
404 For TLS and DTLS, this means that a close_notify alert has been sent but the
417 For TLS and DTLS, this means that a close_notify alert was sent and the peer's
418 close_notify alert was received.