| /freebsd/crypto/openssl/doc/man3/ |
| H A D | SSL_connect.pod | 5 SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server 11 int SSL_connect(SSL *ssl); 15 SSL_connect() initiates the TLS/SSL handshake with a server. The communication 21 The behaviour of SSL_connect() depends on the underlying BIO. 23 If the underlying BIO is B<blocking>, SSL_connect() will only return once the 26 If the underlying BIO is B<nonblocking>, SSL_connect() will also return 27 when the underlying BIO could not satisfy the needs of SSL_connect() 30 return value of SSL_connect() will yield B<SSL_ERROR_WANT_READ> or 32 taking appropriate action to satisfy the needs of SSL_connect().
|
| H A D | SSL_set_connect_state.pod | 40 When using the L<SSL_connect(3)> or 63 L<SSL_connect(3)>, L<SSL_accept(3)>,
|
| H A D | SSL_set_retry_verify.pod | 52 L<ssl(7)>, L<SSL_connect(3)>, L<SSL_CTX_set_cert_verify_callback(3)>,
|
| H A D | SSL_get_verify_result.pod | 29 from the error stack there, because once L<SSL_connect(3)> returns,
|
| H A D | SSL_set_session.pod | 19 again during SSL_connect(). Whether the session was reused can be queried
|
| H A D | SSL_set_fd.pod | 66 L<SSL_connect(3)>, L<SSL_accept(3)>,
|
| H A D | SSL_do_handshake.pod | 68 L<SSL_get_error(3)>, L<SSL_connect(3)>,
|
| H A D | SSL_read.pod | 35 explicitly performed by L<SSL_connect(3)> or L<SSL_accept(3)>. If the 141 L<SSL_connect(3)>, L<SSL_accept(3)>
|
| H A D | SSL_accept.pod | 67 L<SSL_get_error(3)>, L<SSL_connect(3)>,
|
| /freebsd/crypto/openssl/test/ |
| H A D | dtlstest.c | 504 if (!TEST_int_le(SSL_connect(cssl), 0)) in test_swap_records() 512 if (!TEST_int_le(SSL_connect(cssl), 0)) in test_swap_records() 553 if (!TEST_int_gt(SSL_connect(cssl), 0)) in test_swap_records() 617 if (!TEST_int_le(SSL_connect(cssl), 0)) in test_duplicate_app_data() 625 if (!TEST_int_le(SSL_connect(cssl), 0)) in test_duplicate_app_data() 654 if (!TEST_int_gt(SSL_connect(cssl), 0)) in test_duplicate_app_data()
|
| H A D | servername_test.c | 130 if (!TEST_int_le(SSL_connect(con), 0)) in client_setup_sni_before_state() 183 if (!TEST_int_le(SSL_connect(con), 0)) in client_setup_sni_after_state()
|
| H A D | tls13ccstest.c | 356 if (!TEST_int_gt(SSL_connect(cssl), 0)) in test_tls13ccs() 359 if (!TEST_int_le(SSL_connect(cssl), 0)) in test_tls13ccs()
|
| H A D | clienthellotest.c | 150 if (!TEST_int_le(SSL_connect(con), 0)) { in test_client_hello()
|
| H A D | quic_client_test.c | 109 ret = SSL_connect(c_ssl); in test_quic_client_ex()
|
| /freebsd/crypto/openssl/demos/sslecho/ |
| H A D | README.md | 18 SSL_connect().
|
| H A D | main.c | 313 if (SSL_connect(ssl) == 1) { in main()
|
| /freebsd/contrib/libpcap/ |
| H A D | sslutils.c | 150 if (SSL_connect(ssl) <= 0) { in ssl_promotion()
|
| /freebsd/crypto/openssl/demos/guide/ |
| H A D | tls-client-block.c | 203 if (SSL_connect(ssl) < 1) { in main()
|
| H A D | quic-client-block.c | 225 if (SSL_connect(ssl) < 1) { in main()
|
| H A D | tls-client-non-block.c | 282 while ((ret = SSL_connect(ssl)) != 1) { in main()
|
| H A D | quic-multi-stream.c | 252 if (SSL_connect(ssl) < 1) { in main()
|
| H A D | quic-client-non-block.c | 344 while ((ret = SSL_connect(ssl)) != 1) { in main()
|
| /freebsd/contrib/dma/ |
| H A D | crypto.c | 190 error = SSL_connect(config.ssl); in smtp_init_crypto()
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | ossl-guide-tls-client-non-block.pod | 223 As in the demo for a blocking TLS client we use the L<SSL_connect(3)> function 227 In such a case we must retry the same L<SSL_connect(3)> call at a later time. 231 while ((ret = SSL_connect(ssl)) != 1) { 238 We continually call L<SSL_connect(3)> until it gives us a success response. 246 send data to the server. As with L<SSL_connect(3)> above, because we are using
|
| H A D | ossl-guide-quic-client-non-block.pod | 311 As in the demo for a blocking QUIC client we use the L<SSL_connect(3)> function 315 messages. In such a case we must retry the same L<SSL_connect(3)> call at a 319 while ((ret = SSL_connect(ssl)) != 1) { 326 We continually call L<SSL_connect(3)> until it gives us a success response. 334 send data to the server. As with L<SSL_connect(3)> above, because we are using
|