diff --git a/doc/ssl/SSL_accept.pod b/doc/ssl/SSL_accept.pod index ac6caf9baafc8cd514bdf2a91d3917202fd6f73f..a673edba8532723a022a018c89d8e4c38211ca09 100644 --- a/doc/ssl/SSL_accept.pod +++ b/doc/ssl/SSL_accept.pod @@ -69,6 +69,7 @@ to find out the reason. L, L, L, L, L, L, +L, L =cut diff --git a/doc/ssl/SSL_connect.pod b/doc/ssl/SSL_connect.pod index 766f1876aafc408158232a4f0ece6488bac24c81..8426310c0d268e975700cc75aab77140613c00b3 100644 --- a/doc/ssl/SSL_connect.pod +++ b/doc/ssl/SSL_connect.pod @@ -66,6 +66,7 @@ to find out the reason. L, L, L, L, L, L, +L, L =cut diff --git a/doc/ssl/SSL_do_handshake.pod b/doc/ssl/SSL_do_handshake.pod new file mode 100644 index 0000000000000000000000000000000000000000..243576451b7fa77d51f91021d37406f310d9e3dd --- /dev/null +++ b/doc/ssl/SSL_do_handshake.pod @@ -0,0 +1,75 @@ +=pod + +=head1 NAME + +SSL_do_handshake - perform a TLS/SSL handshake + +=head1 SYNOPSIS + + #include + + int SSL_do_handshake(SSL *ssl); + +=head1 DESCRIPTION + +SSL_do_handshake() will wait for a SSL/TLS handshake to take place. If the +connection is in client mode, the handshake will be started. The handshake +routines may have to be explicitly set in advance using either +L or +L. + +=head1 NOTES + +The behaviour of SSL_do_handshake() depends on the underlying BIO. + +If the underlying BIO is B, SSL_do_handshake() will only return +once the handshake has been finished or an error occurred, except for SGC +(Server Gated Cryptography). For SGC, SSL_do_handshake() may return with -1, +but SSL_get_error() will yield B and +SSL_do_handshake() should be called again. + +If the underlying BIO is B, SSL_do_handshake() will also return +when the underlying BIO could not satisfy the needs of SSL_do_handshake() +to continue the handshake. In this case a call to SSL_get_error() with the +return value of SSL_do_handshake() will yield B or +B. The calling process then must repeat the call after +taking appropriate action to satisfy the needs of SSL_do_handshake(). +The action depends on the underlying BIO. When using a non-blocking socket, +nothing is to be done, but select() can be used to check for the required +condition. When using a buffering BIO, like a BIO pair, data must be written +into or retrieved out of the BIO before being able to continue. + +=head1 RETURN VALUES + +The following return values can occur: + +=over 4 + +=item 1 + +The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been +established. + +=item 0 + +The TLS/SSL handshake was not successful but was shut down controlled and +by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the +return value B to find out the reason. + +=item E0 + +The TLS/SSL handshake was not successful because a fatal error occurred either +at the protocol level or a connection failure occurred. The shutdown was +not clean. It can also occur of action is need to continue the operation +for non-blocking BIOs. Call SSL_get_error() with the return value B +to find out the reason. + +=back + +=head1 SEE ALSO + +L, L, +L, L, L, +L + +=cut diff --git a/doc/ssl/SSL_set_connect_state.pod b/doc/ssl/SSL_set_connect_state.pod index 7adf8adfed10d4abcf0c951e5eb59a1bdba96555..d88a057deffa48f2aca19e56f5e7560428f1d9fd 100644 --- a/doc/ssl/SSL_set_connect_state.pod +++ b/doc/ssl/SSL_set_connect_state.pod @@ -49,6 +49,7 @@ information. L, L, L, L, L, L, L, +L, L =cut diff --git a/doc/ssl/ssl.pod b/doc/ssl/ssl.pod index d0525582b06d47f82e6ca4c330db07324d28d1a2..1471e0312e521cb23f96dea9c951902e5c52de69 100644 --- a/doc/ssl/ssl.pod +++ b/doc/ssl/ssl.pod @@ -693,6 +693,7 @@ L, L, L, L, +L, L, L, L,