Lines Matching full:application

68 shutdown process was first initiated by the local application or by the peer.
82 application's shutdown indication.
90 close_notify alert message, an application will be notified of this as an EOF
93 return B<SSL_ERROR_ZERO_RETURN>), after all application data sent by the peer
94 prior to initiating the shutdown has been read. An application should handle
97 application data using L<SSL_write(3)> before doing so. If an application does
117 An application can then detect completion of the shutdown process by calling
125 peer's close_notify alert is still provided to the application. It also ensures
131 it is called when the application has not read all pending application data
143 Alternatively, it is acceptable for an application to call SSL_shutdown() once
146 if the application does not wish to wait for the peer.
150 application exposing itself to a truncation attack. The full SSL_shutdown()
181 application protocol in use enables the peer to ensure that all data has been
183 application data may be truncated unexpectedly.
195 Note that use of this option means that the EOF condition for application data
196 does not receive cryptographic protection, and therefore renders an application
198 used in conjunction with an application protocol which indicates unambiguously
202 that no more data is going to be sent. This requires an application protocol
207 If a client application only writes to an SSL/TLS or DTLS connection and never
210 peer during calls to L<SSL_read(3)> by the application.
227 SSL_shutdown_ex() may be used instead of SSL_shutdown() by an application to
235 An optional 62-bit application error code to be signalled to the peer. The value
242 The application is responsible for providing a valid UTF-8 string and OpenSSL
251 be used for application signalling.
263 Note that when using QUIC, an application must call SSL_shutdown() if it wants
266 responsibility of the operating system. If an application calls SSL_free() on a
268 SSL_shutdown(), data which was written by the application using SSL_write(), but
274 whether during connection usage or during shutdown. If an application is not
275 using thread assisted mode, an application conducting shutdown should either
280 =head2 Application Data Drainage Behaviour
283 data written to a stream by an application has been acknowledged by the peer. In
285 application has been sent to the peer, and until the receipt of all such data is
297 be transmitted to the peer. This flag may be used when a non-normal application
310 processes which need to exit immediately after completing an application-layer
346 If an application calls SSL_shutdown_ex() with B<SSL_SHUTDOWN_FLAG_RAPID>, an
347 application can subsequently change its mind about performing a rapid shutdown
352 In some cases, an application may wish to wait for a shutdown initiated by the