ssl_set_connect_state(3openssl) [opensolaris man page]
SSL_set_connect_state(3openssl) OpenSSL SSL_set_connect_state(3openssl) 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_ver- sion(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 transpar- ent negotiation using SSL_write(3) or SSL_read(3), the handshake routines must be explicitly set in advance using either SSL_set_con- nect_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_ver- sion(3) OpenSSL-0.9.8 Oct 11 2005 SSL_set_connect_state(3openssl)
Check Out this Related Man Page
SSL_connect(3openssl) OpenSSL SSL_connect(3openssl) NAME
SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server SYNOPSIS
#include <openssl/ssl.h> int SSL_connect(SSL *ssl); DESCRIPTION
SSL_connect() initiates the TLS/SSL handshake with a server. The communication channel must already have been set and assigned to the ssl by setting an underlying BIO. NOTES
The behaviour of SSL_connect() depends on the underlying BIO. If the underlying BIO is blocking, SSL_connect() will only return once the handshake has been finished or an error occurred. If the underlying BIO is non-blocking, SSL_connect() will also return when the underlying BIO could not satisfy the needs of SSL_connect() to continue the handshake, indicating the problem by the return value -1. In this case a call to SSL_get_error() with the return value of SSL_connect() will yield SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE. The calling process then must repeat the call after taking appropri- ate action to satisfy the needs of SSL_connect(). 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_accept(3), SSL_shutdown(3), ssl(3), bio(3), SSL_set_connect_state(3), SSL_do_handshake(3), SSL_CTX_new(3) OpenSSL-0.9.8 Oct 11 2005 SSL_connect(3openssl)