ssl_set_connect_state(3ssl) [ultrix man page]

SSL_set_connect_state(3SSL)					      OpenSSL					       SSL_set_connect_state(3SSL)

NAME

       SSL_set_connect_state, SSL_get_accept_state - prepare SSL object to work in client or server mode

SYNOPSIS

	#include <openssl/ssl.h>

	void SSL_set_connect_state(SSL *ssl);

	void SSL_set_accept_state(SSL *ssl);

DESCRIPTION

       SSL_set_connect_state() sets ssl to work in client mode.

       SSL_set_accept_state() sets ssl to work in server mode.

NOTES

       When the SSL_CTX object was created with SSL_CTX_new(3), it was either assigned a dedicated client method, a dedicated server method, or a
       generic method, that can be used for both client and server connections. (The method might have been changed with
       SSL_CTX_set_ssl_version(3) or SSL_set_ssl_method().)

       When beginning a new handshake, the SSL engine must know whether it must call the connect (client) or accept (server) routines. Even though
       it may be clear from the method chosen, whether client or server mode was requested, the handshake routines must be explicitly set.

       When using the SSL_connect(3) or SSL_accept(3) routines, the correct handshake routines are automatically set. When performing a
       transparent negotiation using SSL_write(3) or SSL_read(3), the handshake routines must be explicitly set in advance using either
       SSL_set_connect_state() or SSL_set_accept_state().

RETURN VALUES

       SSL_set_connect_state() and SSL_set_accept_state() do not return diagnostic information.

SEE ALSO

       ssl(3), SSL_new(3), SSL_CTX_new(3), SSL_connect(3), SSL_accept(3), SSL_write(3), SSL_read(3), SSL_do_handshake(3),
       SSL_CTX_set_ssl_version(3)

1.0.1e								    2013-02-11					       SSL_set_connect_state(3SSL)

SSL_do_handshake(3SSL)						      OpenSSL						    SSL_do_handshake(3SSL)

NAME

       SSL_do_handshake - perform a TLS/SSL handshake

SYNOPSIS

	#include <openssl/ssl.h>

	int SSL_do_handshake(SSL *ssl);

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 SSL_set_connect_state(3) or SSL_set_accept_state(3).

NOTES

       The behaviour of SSL_do_handshake() depends on the underlying BIO.

       If the underlying BIO is blocking, 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
       SSL_ERROR_WANT_READ/WRITE and SSL_do_handshake() should be called again.

       If the underlying BIO is non-blocking, 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
       SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. 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.

RETURN VALUES

       The following return values can occur:

       1.  The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established.

       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 ret to find out the reason.

       <0  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 ret to find out the reason.

SEE ALSO

       SSL_get_error(3), SSL_connect(3), SSL_accept(3), ssl(3), bio(3), SSL_set_connect_state(3)

1.0.1e								    2014-08-06						    SSL_do_handshake(3SSL)