SSL_accept.pod 2.5 KB

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