Lines Matching +full:- +full:alert
18 .\" Set up some character translations and predefined strings. \*(-- will
24 .tr \(*W-
27 . ds -- \(*W-
29 . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
30 . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
37 . ds -- \|\(em\|
71 .\" Fear. Run. Save yourself. No user-serviceable parts.
81 . ds #H ((1u-(\\\\n(.fu%2u))*.13m)
97 . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
98 . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
99 . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
100 . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
101 . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
102 . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
104 . \" troff and (daisy-wheel) nroff accents
123 . ds d- d\h'-1'\(ga
124 . ds D- D\h'-1'\(hy
134 .TH SSL_SHUTDOWN 3ossl "2023-09-19" "3.0.11" "OpenSSL"
140 SSL_shutdown \- shut down a TLS/SSL connection
150 \&\fBSSL_shutdown()\fR shuts down an active \s-1TLS/SSL\s0 connection. It sends the
151 close_notify shutdown alert to the peer.
153 \&\fBSSL_shutdown()\fR tries to send the close_notify shutdown alert to the peer.
154 Whether the operation succeeds or not, the \s-1SSL_SENT_SHUTDOWN\s0 flag is set and
159 occurred on a connection i.e. if \fBSSL_get_error()\fR has returned \s-1SSL_ERROR_SYSCALL\s0
160 or \s-1SSL_ERROR_SSL.\s0
163 shutdown alert, and reception of the peer's close_notify shutdown alert.
166 It is acceptable for an application to only send its shutdown alert and
188 The behaviour of \fBSSL_shutdown()\fR additionally depends on the underlying \s-1BIO.\s0
189 If the underlying \s-1BIO\s0 is \fBblocking\fR, \fBSSL_shutdown()\fR will only return once the
192 If the underlying \s-1BIO\s0 is \fBnonblocking\fR, \fBSSL_shutdown()\fR will also return
193 when the underlying \s-1BIO\s0 could not satisfy the needs of \fBSSL_shutdown()\fR
195 return value of \fBSSL_shutdown()\fR will yield \fB\s-1SSL_ERROR_WANT_READ\s0\fR or
196 \&\fB\s-1SSL_ERROR_WANT_WRITE\s0\fR. The calling process then must repeat the call after
198 The action depends on the underlying \s-1BIO.\s0 When using a nonblocking socket,
200 condition. When using a buffering \s-1BIO,\s0 like a \s-1BIO\s0 pair, data must be written
201 into or retrieved out of the \s-1BIO\s0 before being able to continue.
204 to wait for the peer's close_notify alert.
209 state but not actually send the close_notify alert messages,
215 data has been received and doesn't wait for the close_notify alert
216 message, otherwise an unexpected \s-1EOF\s0 will be reported.
218 There are implementations that do not send the required close_notify alert.
220 that all data has been received, do not wait for the peer's close_notify alert.
221 Waiting for the close_notify alert when the peer just closes the connection
223 The error can be ignored using the \fB\s-1SSL_OP_IGNORE_UNEXPECTED_EOF\s0\fR.
228 alert, \fBSSL_shutdown()\fR will only send the alert and then set the
229 \&\s-1SSL_SENT_SHUTDOWN\s0 flag (so that the session is considered good and will
237 to send back a close_notify alert.
238 The \s-1SSL_RECEIVED_SHUTDOWN\s0 flag will be set after receiving and processing
243 When it is done sending data, it will send the close_notify alert.
246 and \fBSSL_get_error()\fR returning \s-1SSL_ERROR_ZERO_RETURN.\s0
249 If the peer already sent the close_notify alert \fBand\fR it was
251 (\fBSSL_read\fR\|(3)), the \s-1SSL_RECEIVED_SHUTDOWN\s0 flag is set.
253 \&\s-1SSL_ERROR_ZERO_RETURN.\s0
254 \&\fBSSL_shutdown()\fR will send the close_notify alert, set the \s-1SSL_SENT_SHUTDOWN\s0
258 Whether \s-1SSL_RECEIVED_SHUTDOWN\s0 is already set can be checked using the
273 The shutdown was successfully completed. The close_notify alert was sent
274 and the peer's close_notify alert was received.
292 Copyright 2000\-2020 The OpenSSL Project Authors. All Rights Reserved.
296 in the file \s-1LICENSE\s0 in the source distribution or at