Automatically generated by Pod::Man 4.14 (Pod::Simple 3.42)

Standard preamble:
========================================================================
..

..

.. Set up some character translations and predefined strings. \*(-- will
give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
double quote, and \*(R" will give a right double quote. \*(C+ will
give a nicer C++. Capital omega is used to do unbreakable dashes and
therefore won't be available. \*(C` and \*(C' expand to `' in nroff,
nothing in troff, for use with C<>.
.tr \(*W- . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

If the F register is >0, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.

Avoid warning from groff about undefined register 'F'.
.. .nr rF 0 . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] .\} . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents . \" corrections for vroff . \" for low resolution devices (crt and lpr) \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} ========================================================================

Title "SSL_SHUTDOWN 3ossl" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
SSL_shutdown - shut down a TLS/SSL connection Header "SYNOPSIS" .Vb 1 #include <openssl/ssl.h> \& int SSL_shutdown(SSL *ssl); .Ve Header "DESCRIPTION" \fBSSL_shutdown() shuts down an active \s-1TLS/SSL\s0 connection. It sends the close_notify shutdown alert to the peer.

\fBSSL_shutdown() tries to send the close_notify shutdown alert to the peer. Whether the operation succeeds or not, the \s-1SSL_SENT_SHUTDOWN\s0 flag is set and a currently open session is considered closed and good and will be kept in the session cache for further reuse.

Note that SSL_shutdown() must not be called if a previous fatal error has occurred on a connection i.e. if SSL_get_error() has returned \s-1SSL_ERROR_SYSCALL\s0 or \s-1SSL_ERROR_SSL.\s0

The shutdown procedure consists of two steps: sending of the close_notify shutdown alert, and reception of the peer's close_notify shutdown alert. The order of those two steps depends on the application.

It is acceptable for an application to only send its shutdown alert and then close the underlying connection without waiting for the peer's response. This way resources can be saved, as the process can already terminate or serve another connection. This should only be done when it is known that the other side will not send more data, otherwise there is a risk of a truncation attack.

When a client only writes and never reads from the connection, and the server has sent a session ticket to establish a session, the client might not be able to resume the session because it did not received and process the session ticket from the server. In case the application wants to be able to resume the session, it is recommended to do a complete shutdown procedure (bidirectional close_notify alerts).

When the underlying connection shall be used for more communications, the complete shutdown procedure must be performed, so that the peers stay synchronized.

\fBSSL_shutdown() only closes the write direction. It is not possible to call SSL_write() after calling SSL_shutdown(). The read direction is closed by the peer.

The behaviour of SSL_shutdown() additionally depends on the underlying \s-1BIO.\s0 If the underlying \s-1BIO\s0 is blocking, SSL_shutdown() will only return once the handshake step has been finished or an error occurred.

If the underlying \s-1BIO\s0 is nonblocking, SSL_shutdown() will also return when the underlying \s-1BIO\s0 could not satisfy the needs of SSL_shutdown() to continue the handshake. In this case a call to SSL_get_error() with the return value of SSL_shutdown() will yield \s-1SSL_ERROR_WANT_READ\s0 or \fB\s-1SSL_ERROR_WANT_WRITE\s0. The calling process then must repeat the call after taking appropriate action to satisfy the needs of SSL_shutdown(). The action depends on the underlying \s-1BIO.\s0 When using a nonblocking socket, nothing is to be done, but select() can be used to check for the required condition. When using a buffering \s-1BIO,\s0 like a \s-1BIO\s0 pair, data must be written into or retrieved out of the \s-1BIO\s0 before being able to continue.

After SSL_shutdown() returned 0, it is possible to call SSL_shutdown() again to wait for the peer's close_notify alert. \fBSSL_shutdown() will return 1 in that case. However, it is recommended to wait for it using SSL_read() instead.

\fBSSL_shutdown() can be modified to only set the connection to \*(L"shutdown\*(R" state but not actually send the close_notify alert messages, see SSL_CTX_set_quiet_shutdown\|(3). When \*(L"quiet shutdown\*(R" is enabled, SSL_shutdown() will always succeed and return 1. Note that this is not standard compliant behaviour. It should only be done when the peer has a way to make sure all data has been received and doesn't wait for the close_notify alert message, otherwise an unexpected \s-1EOF\s0 will be reported.

There are implementations that do not send the required close_notify alert. If there is a need to communicate with such an implementation, and it's clear that all data has been received, do not wait for the peer's close_notify alert. Waiting for the close_notify alert when the peer just closes the connection will result in an error being generated. The error can be ignored using the \s-1SSL_OP_IGNORE_UNEXPECTED_EOF\s0. For more information see SSL_CTX_set_options\|(3).

Subsection "First to close the connection" When the application is the first party to send the close_notify alert, SSL_shutdown() will only send the alert and then set the \s-1SSL_SENT_SHUTDOWN\s0 flag (so that the session is considered good and will be kept in the cache). If successful, SSL_shutdown() will return 0.

If a unidirectional shutdown is enough (the underlying connection shall be closed anyway), this first successful call to SSL_shutdown() is sufficient.

In order to complete the bidirectional shutdown handshake, the peer needs to send back a close_notify alert. The \s-1SSL_RECEIVED_SHUTDOWN\s0 flag will be set after receiving and processing it.

The peer is still allowed to send data after receiving the close_notify event. When it is done sending data, it will send the close_notify alert. \fBSSL_read() should be called until all data is received. \fBSSL_read() will indicate the end of the peer data by returning <= 0 and SSL_get_error() returning \s-1SSL_ERROR_ZERO_RETURN.\s0

Subsection "Peer closes the connection" If the peer already sent the close_notify alert and it was already processed implicitly inside another function (SSL_read\|(3)), the \s-1SSL_RECEIVED_SHUTDOWN\s0 flag is set. \fBSSL_read() will return <= 0 in that case, and SSL_get_error() will return \s-1SSL_ERROR_ZERO_RETURN.\s0 \fBSSL_shutdown() will send the close_notify alert, set the \s-1SSL_SENT_SHUTDOWN\s0 flag. If successful, SSL_shutdown() will return 1.

Whether \s-1SSL_RECEIVED_SHUTDOWN\s0 is already set can be checked using the \fBSSL_get_shutdown() (see also SSL_set_shutdown\|(3) call.

Header "RETURN VALUES" The following return values can occur: The shutdown is not yet finished: the close_notify was sent but the peer did not send it back yet. Call SSL_read() to do a bidirectional shutdown. .Sp Unlike most other function, returning 0 does not indicate an error. \fBSSL_get_error\|(3) should not get called, it may misleadingly indicate an error even though no error occurred. Item "1" The shutdown was successfully completed. The close_notify alert was sent and the peer's close_notify alert was received. Item "<0" The shutdown was not successful. Call SSL_get_error\|(3) with the return value ret to find out the reason. It can occur if an action is needed to continue the operation for nonblocking BIOs. .Sp It can also occur when not all data was read using SSL_read(). Header "SEE ALSO" \fBSSL_get_error\|(3), SSL_connect\|(3), \fBSSL_accept\|(3), SSL_set_shutdown\|(3), \fBSSL_CTX_set_quiet_shutdown\|(3), SSL_CTX_set_options\|(3) \fBSSL_clear\|(3), SSL_free\|(3), \fBssl\|(7), bio\|(7) Header "COPYRIGHT" Copyright 2000-2020 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the \*(L"License\*(R"). You may not use this file except in compliance with the License. You can obtain a copy in the file \s-1LICENSE\s0 in the source distribution or at <https://www.openssl.org/source/license.html>.