yuezonghe | 824eb0c | 2024-06-27 02:32:26 -0700 | [diff] [blame] | 1 | =pod |
| 2 | |
| 3 | =head1 NAME |
| 4 | |
| 5 | SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server |
| 6 | |
| 7 | =head1 SYNOPSIS |
| 8 | |
| 9 | #include <openssl/ssl.h> |
| 10 | |
| 11 | int SSL_connect(SSL *ssl); |
| 12 | |
| 13 | =head1 DESCRIPTION |
| 14 | |
| 15 | SSL_connect() initiates the TLS/SSL handshake with a server. The communication |
| 16 | channel must already have been set and assigned to the B<ssl> by setting an |
| 17 | underlying B<BIO>. |
| 18 | |
| 19 | =head1 NOTES |
| 20 | |
| 21 | The behaviour of SSL_connect() depends on the underlying BIO. |
| 22 | |
| 23 | If the underlying BIO is B<blocking>, SSL_connect() will only return once the |
| 24 | handshake has been finished or an error occurred. |
| 25 | |
| 26 | If the underlying BIO is B<nonblocking>, SSL_connect() will also return |
| 27 | when the underlying BIO could not satisfy the needs of SSL_connect() |
| 28 | to continue the handshake, indicating the problem by the return value -1. |
| 29 | In this case a call to SSL_get_error() with the |
| 30 | return value of SSL_connect() will yield B<SSL_ERROR_WANT_READ> or |
| 31 | B<SSL_ERROR_WANT_WRITE>. The calling process then must repeat the call after |
| 32 | taking appropriate action to satisfy the needs of SSL_connect(). |
| 33 | The action depends on the underlying BIO. When using a nonblocking socket, |
| 34 | nothing is to be done, but select() can be used to check for the required |
| 35 | condition. When using a buffering BIO, like a BIO pair, data must be written |
| 36 | into or retrieved out of the BIO before being able to continue. |
| 37 | |
| 38 | Many systems implement Nagle's algorithm by default which means that it will |
| 39 | buffer outgoing TCP data if a TCP packet has already been sent for which no |
| 40 | corresponding ACK has been received yet from the peer. This can have performance |
| 41 | impacts after a successful TLSv1.3 handshake or a successful TLSv1.2 (or below) |
| 42 | resumption handshake, because the last peer to communicate in the handshake is |
| 43 | the client. If the client is also the first to send application data (as is |
| 44 | typical for many protocols) then this data could be buffered until an ACK has |
| 45 | been received for the final handshake message. |
| 46 | |
| 47 | The B<TCP_NODELAY> socket option is often available to disable Nagle's |
| 48 | algorithm. If an application opts to disable Nagle's algorithm consideration |
| 49 | should be given to turning it back on again later if appropriate. The helper |
| 50 | function BIO_set_tcp_ndelay() can be used to turn on or off the B<TCP_NODELAY> |
| 51 | option. |
| 52 | |
| 53 | =head1 RETURN VALUES |
| 54 | |
| 55 | The following return values can occur: |
| 56 | |
| 57 | =over 4 |
| 58 | |
| 59 | =item Z<>0 |
| 60 | |
| 61 | The TLS/SSL handshake was not successful but was shut down controlled and |
| 62 | by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the |
| 63 | return value B<ret> to find out the reason. |
| 64 | |
| 65 | =item Z<>1 |
| 66 | |
| 67 | The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been |
| 68 | established. |
| 69 | |
| 70 | =item E<lt>0 |
| 71 | |
| 72 | The TLS/SSL handshake was not successful, because a fatal error occurred either |
| 73 | at the protocol level or a connection failure occurred. The shutdown was |
| 74 | not clean. It can also occur if action is needed to continue the operation |
| 75 | for nonblocking BIOs. Call SSL_get_error() with the return value B<ret> |
| 76 | to find out the reason. |
| 77 | |
| 78 | =back |
| 79 | |
| 80 | =head1 SEE ALSO |
| 81 | |
| 82 | L<SSL_get_error(3)>, L<SSL_accept(3)>, |
| 83 | L<SSL_shutdown(3)>, L<ssl(7)>, L<bio(7)>, |
| 84 | L<SSL_set_connect_state(3)>, |
| 85 | L<SSL_do_handshake(3)>, |
| 86 | L<SSL_CTX_new(3)> |
| 87 | |
| 88 | =head1 COPYRIGHT |
| 89 | |
| 90 | Copyright 2000-2020 The OpenSSL Project Authors. All Rights Reserved. |
| 91 | |
| 92 | Licensed under the OpenSSL license (the "License"). You may not use |
| 93 | this file except in compliance with the License. You can obtain a copy |
| 94 | in the file LICENSE in the source distribution or at |
| 95 | L<https://www.openssl.org/source/license.html>. |
| 96 | |
| 97 | =cut |