SSL_connect.pod 2.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172
  1. =pod
  2. =head1 NAME
  3. SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server
  4. =head1 SYNOPSIS
  5. #include <openssl/ssl.h>
  6. int SSL_connect(SSL *ssl);
  7. =head1 DESCRIPTION
  8. SSL_connect() initiates the TLS/SSL handshake with a server. The communication
  9. channel must already have been set and assigned to the B<ssl> by setting an
  10. underlying B<BIO>.
  11. =head1 NOTES
  12. The behaviour of SSL_connect() depends on the underlying BIO.
  13. If the underlying BIO is B<blocking>, SSL_connect() will only return once the
  14. handshake has been finished or an error occurred.
  15. If the underlying BIO is B<non-blocking>, SSL_connect() will also return
  16. when the underlying BIO could not satisfy the needs of SSL_connect()
  17. to continue the handshake. In this case a call to SSL_get_error() with the
  18. return value of SSL_connect() will yield B<SSL_ERROR_WANT_READ> or
  19. B<SSL_ERROR_WANT_WRITE>. The calling process then must repeat the call after
  20. taking appropriate action to satisfy the needs of SSL_connect().
  21. The action depends on the underlying BIO. When using a non-blocking socket,
  22. nothing is to be done, but select() can be used to check for the required
  23. condition. When using a buffering BIO, like a BIO pair, data must be written
  24. into or retrieved out of the BIO before being able to continue.
  25. =head1 RETURN VALUES
  26. The following return values can occur:
  27. =over 4
  28. =item 1
  29. The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
  30. established.
  31. =item 0
  32. The TLS/SSL handshake was not successful but was shut down controlled and
  33. by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
  34. return value B<ret> to find out the reason.
  35. =item E<lt>0
  36. The TLS/SSL handshake was not successful, because a fatal error occurred either
  37. at the protocol level or a connection failure occurred. The shutdown was
  38. not clean. It can also occur of action is need to continue the operation
  39. for non-blocking BIOs. Call SSL_get_error() with the return value B<ret>
  40. to find out the reason.
  41. =back
  42. =head1 SEE ALSO
  43. L<SSL_get_error(3)|SSL_get_error(3)>, L<SSL_accept(3)|SSL_accept(3)>,
  44. L<SSL_shutdown(3)|SSL_shutdown(3)>, L<ssl(3)|ssl(3)>, L<bio(3)|bio(3)>,
  45. L<SSL_set_connect_state(3)|SSL_set_connect_state(3)>,
  46. L<SSL_do_handshake(3)|SSL_do_handshake(3)>,
  47. L<SSL_CTX_new(3)|SSL_CTX_new(3)>
  48. =cut