$NetBSD: SSL_set_connect_state.3,v 1.25 2024/09/08 13:08:35 christos Exp $

-*- mode: troff; coding: utf-8 -*-
Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)

Standard preamble:
========================================================================
..

..

.. \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
. ds C` "" . ds C' "" 'br\} . ds C` . ds C' 'br\}
Escape single quotes in literal strings from groff's Unicode transform.

If the F register is >0, we'll generate index entries on stderr for
titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
entries marked with X<> in POD. Of course, you'll have to process the
output yourself in some meaningful fashion.

Avoid warning from groff about undefined register 'F'.
.. .nr rF 0 . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF ========================================================================

Title "SSL_set_connect_state 3" For nroff, turn off justification. Always turn off hyphenation; it makes
way too many mistakes in technical documents.
SSL_set_connect_state, SSL_set_accept_state, SSL_is_server \- functions for manipulating and examining the client or server mode of an SSL object Header "SYNOPSIS" .Vb 1 #include <openssl/ssl.h> \& void SSL_set_connect_state(SSL *ssl); \& void SSL_set_accept_state(SSL *ssl); \& int SSL_is_server(const SSL *ssl); .Ve Header "DESCRIPTION" \fBSSL_set_connect_state() sets ssl to work in client mode.

\fBSSL_set_accept_state() sets ssl to work in server mode.

\fBSSL_is_server() checks if ssl is working in server mode.

Header "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 \fBSSL_CTX_set_ssl_version\|(3) or \fBSSL_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 \fBSSL_accept\|(3) routines, the correct handshake routines are automatically set. When performing a transparent negotiation using SSL_write_ex\|(3), SSL_write\|(3), SSL_read_ex\|(3), or SSL_read\|(3), the handshake routines must be explicitly set in advance using either \fBSSL_set_connect_state() or SSL_set_accept_state().

If SSL_is_server() is called before SSL_set_connect_state() or \fBSSL_set_accept_state() is called (either automatically or explicitly), the result depends on what method was used when SSL_CTX was created with \fBSSL_CTX_new\|(3). If a generic method or a dedicated server method was passed to SSL_CTX_new\|(3), SSL_is_server() returns 1; otherwise, it returns 0.

Header "RETURN VALUES" \fBSSL_set_connect_state() and SSL_set_accept_state() do not return diagnostic information.

\fBSSL_is_server() returns 1 if ssl is working in server mode or 0 for client mode.

Header "SEE ALSO" \fBssl\|(7), SSL_new\|(3), SSL_CTX_new\|(3), \fBSSL_connect\|(3), SSL_accept\|(3), \fBSSL_write_ex\|(3), SSL_write\|(3), SSL_read_ex\|(3), SSL_read\|(3), \fBSSL_do_handshake\|(3), \fBSSL_CTX_set_ssl_version\|(3) Header "COPYRIGHT" Copyright 2001-2017 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.