Lines Matching refs:SSL_shutdown
5 SSL_shutdown, SSL_shutdown_ex - shut down a TLS/SSL or QUIC connection
11 int SSL_shutdown(SSL *ssl);
24 SSL_shutdown() shuts down an active connection represented by an SSL object. I<ssl> B<MUST NOT> be …
26 SSL_shutdown_ex() is an extended version of SSL_shutdown(). If non-NULL, I<args>
32 to SSL_shutdown() when not being used with QUIC.
34 While the general operation of SSL_shutdown() is common between protocols, the
39 In general, calling SSL_shutdown() in nonblocking mode will initiate the
42 SSL_shutdown() will return 1. See the RETURN VALUES section for more
45 SSL_shutdown() should not be called if a previous fatal error has occurred on a
72 Calling SSL_shutdown() on an SSL/TLS or DTLS SSL object initiates the shutdown
77 Calling SSL_shutdown() only closes the write direction of the connection; the
78 read direction is closed by the peer. Once SSL_shutdown() is called,
84 SSL_shutdown() does not affect an underlying network connection such as a TCP
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
104 underlying BIO is blocking, a call to SSL_shutdown() will return firstly once a
107 peer (returning 1 and completing the shutdown process). Calls to SSL_shutdown()
113 but would currently block), SSL_shutdown() returns 0 to indicate that the
118 SSL_shutdown() again repeatedly until it returns 1, indicating that the shutdown
129 If this approach is not used, the second call to SSL_shutdown() (to complete the
134 When calling SSL_shutdown(), the B<SSL_SENT_SHUTDOWN> flag is set once an
138 from the network, such as L<SSL_read(3)> or SSL_shutdown(). These flags
143 Alternatively, it is acceptable for an application to call SSL_shutdown() once
150 application exposing itself to a truncation attack. The full SSL_shutdown()
151 process, in which both parties send close_notify alerts and SSL_shutdown()
155 This approach of a single SSL_shutdown() call without waiting is preferable to
156 simply calling L<SSL_free(3)> or L<SSL_clear(3)> as calling SSL_shutdown()
167 Calling SSL_shutdown() sets the SSL_SENT_SHUTDOWN flag (see
175 SSL_shutdown() can be modified to set the connection to the "shutdown"
178 SSL_shutdown() will always succeed and return 1 immediately.
214 procedure by calling SSL_shutdown() until it returns 1, as described above. This
220 When used with a QUIC connection SSL object, SSL_shutdown() initiates a QUIC
223 SSL_shutdown() cannot be used on QUIC stream SSL objects. To conclude a stream
227 SSL_shutdown_ex() may be used instead of SSL_shutdown() by an application to
243 will not validate the string. If a reason is not provided, or SSL_shutdown() is
256 SSL_shutdown_ex() (or SSL_shutdown()) for a given QUIC connection SSL object.
263 Note that when using QUIC, an application must call SSL_shutdown() if it wants
268 SSL_shutdown(), data which was written by the application using SSL_write(), but
272 When using QUIC, calling SSL_shutdown() allows internal network event processing
276 ensure that SSL_shutdown() is called regularly, or alternatively ensure that
282 When using QUIC, SSL_shutdown() or SSL_shutdown_ex() ordinarily waits until all
291 SSL_shutdown() is called, or which terminated in a normal fashion, have their
369 SSL_shutdown() and SSL_shutdown_ex() block if the connection is configured in
376 For both SSL_shutdown() and SSL_shutdown_ex() the following return values can occur:
