diff options
Diffstat (limited to 'src/lib/libssl/doc/SSL_set_connect_state.3')
| -rw-r--r-- | src/lib/libssl/doc/SSL_set_connect_state.3 | 71 |
1 files changed, 0 insertions, 71 deletions
diff --git a/src/lib/libssl/doc/SSL_set_connect_state.3 b/src/lib/libssl/doc/SSL_set_connect_state.3 deleted file mode 100644 index e3f946f8ee..0000000000 --- a/src/lib/libssl/doc/SSL_set_connect_state.3 +++ /dev/null | |||
| @@ -1,71 +0,0 @@ | |||
| 1 | .\" | ||
| 2 | .\" $OpenBSD: SSL_set_connect_state.3,v 1.2 2014/12/02 14:11:01 jmc Exp $ | ||
| 3 | .\" | ||
| 4 | .Dd $Mdocdate: December 2 2014 $ | ||
| 5 | .Dt SSL_SET_CONNECT_STATE 3 | ||
| 6 | .Os | ||
| 7 | .Sh NAME | ||
| 8 | .Nm SSL_set_connect_state , | ||
| 9 | .Nm SSL_get_accept_state | ||
| 10 | .Nd prepare SSL object to work in client or server mode | ||
| 11 | .Sh SYNOPSIS | ||
| 12 | .In openssl/ssl.h | ||
| 13 | .Ft void | ||
| 14 | .Fn SSL_set_connect_state "SSL *ssl" | ||
| 15 | .Ft void | ||
| 16 | .Fn SSL_set_accept_state "SSL *ssl" | ||
| 17 | .Sh DESCRIPTION | ||
| 18 | .Fn SSL_set_connect_state | ||
| 19 | sets | ||
| 20 | .Fa ssl | ||
| 21 | to work in client mode. | ||
| 22 | .Pp | ||
| 23 | .Fn SSL_set_accept_state | ||
| 24 | sets | ||
| 25 | .Fa ssl | ||
| 26 | to work in server mode. | ||
| 27 | .Sh NOTES | ||
| 28 | When the | ||
| 29 | .Vt SSL_CTX | ||
| 30 | object was created with | ||
| 31 | .Xr SSL_CTX_new 3 , | ||
| 32 | it was either assigned a dedicated client method, a dedicated server method, or | ||
| 33 | a generic method, that can be used for both client and server connections. | ||
| 34 | (The method might have been changed with | ||
| 35 | .Xr SSL_CTX_set_ssl_version 3 | ||
| 36 | or | ||
| 37 | .Xr SSL_set_ssl_method 3 . ) | ||
| 38 | .Pp | ||
| 39 | When beginning a new handshake, the SSL engine must know whether it must call | ||
| 40 | the connect (client) or accept (server) routines. | ||
| 41 | Even though it may be clear from the method chosen whether client or server | ||
| 42 | mode was requested, the handshake routines must be explicitly set. | ||
| 43 | .Pp | ||
| 44 | When using the | ||
| 45 | .Xr SSL_connect 3 | ||
| 46 | or | ||
| 47 | .Xr SSL_accept 3 | ||
| 48 | routines, the correct handshake routines are automatically set. | ||
| 49 | When performing a transparent negotiation using | ||
| 50 | .Xr SSL_write 3 | ||
| 51 | or | ||
| 52 | .Xr SSL_read 3 , | ||
| 53 | the handshake routines must be explicitly set in advance using either | ||
| 54 | .Fn SSL_set_connect_state | ||
| 55 | or | ||
| 56 | .Fn SSL_set_accept_state . | ||
| 57 | .Sh RETURN VALUES | ||
| 58 | .Fn SSL_set_connect_state | ||
| 59 | and | ||
| 60 | .Fn SSL_set_accept_state | ||
| 61 | do not return diagnostic information. | ||
| 62 | .Sh SEE ALSO | ||
| 63 | .Xr ssl 3 , | ||
| 64 | .Xr SSL_accept 3 , | ||
| 65 | .Xr SSL_connect 3 , | ||
| 66 | .Xr SSL_CTX_new 3 , | ||
| 67 | .Xr SSL_CTX_set_ssl_version 3 , | ||
| 68 | .Xr SSL_do_handshake 3 , | ||
| 69 | .Xr SSL_new 3 , | ||
| 70 | .Xr SSL_read 3 , | ||
| 71 | .Xr SSL_write 3 | ||