Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   44335 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

SSL_SET_CONNECT_STATE(3) BSD Library Functions Manual SSL_SET_CONNECT_STATE(3)

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

     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 diagnos‐
     tic information.

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

BSD				April 19, 2024				   BSD

Vote for polarhome