Manual Pages for UNIX Operating System command usage for man SSL_accept

OpenSSL                                      SSL_accept(3openssl)



NNNNAAAAMMMMEEEE
     SSL_accept - wait for a TLS/SSL client to initiate a TLS/SSL
     handshake

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
      #include 

      int SSL_accept(SSL *ssl);


DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
     SSL_accept() waits for a TLS/SSL client to initiate the
     TLS/SSL handshake.  The communication channel must already
     have been set and assigned to the ssssssssllll by setting an
     underlying BBBBIIIIOOOO.

NNNNOOOOTTTTEEEESSSS
     The behaviour of SSL_accept() depends on the underlying BIO.

     If the underlying BIO is bbbblllloooocccckkkkiiiinnnngggg, SSL_accept() will only
     return once the handshake has been finished or an error
     occurred, except for SGC (Server Gated Cryptography). For
     SGC, SSL_accept() may return with -1, but SSL_get_error()
     will yield SSSSSSSSLLLL_EEEERRRRRRRROOOORRRR_WWWWAAAANNNNTTTT_RRRREEEEAAAADDDD////WWWWRRRRIIIITTTTEEEE and SSL_accept() should
     be called again.

     If the underlying BIO is nnnnoooonnnn---bbblllloooocccckkkkiiiinnnngggg, SSL_accept() will
     also return when the underlying BIO could not satisfy the
     needs of SSL_accept() to continue the handshake, indicating
     the problem by the return value -1.  In this case a call to
     SSL_get_error() with the return value of SSL_accept() will
     yield SSSSSSSSLLLL_EEEERRRRRRRROOOORRRR_WWWWAAAANNNNTTTT_RRRREEEEAAAADDDD or SSSSSSSSLLLL_EEEERRRRRRRROOOORRRR_WWWWAAAANNNNTTTT_WWWWRRRRIIIITTTTEEEE. The
     calling process then must repeat the call after taking
     appropriate action to satisfy the needs of SSL_accept().
     The action depends on the underlying BIO. When using a non-
     blocking socket, nothing is to be done, but select() can be
     used to check for the required condition. When using a
     buffering BIO, like a BIO pair, data must be written into or
     retrieved out of the BIO before being able to continue.

RRRREEEETTTTUUUURRRRNNNN VVVVAAAALLLLUUUUEEEESSSS
     The following return values can occur:

     1   The TLS/SSL handshake was successfully completed, a
         TLS/SSL connection has been established.

     0   The TLS/SSL handshake was not successful but was shut
         down controlled and by the specifications of the TLS/SSL
         protocol. Call SSL_get_error() with the return value rrrreeeetttt
         to find out the reason.





3/Jun/2003             Last change: 0.9.8o                      1






OpenSSL                                      SSL_accept(3openssl)



     <0  The TLS/SSL handshake was not successful because a fatal
         error occurred either at the protocol level or a
         connection failure occurred. The shutdown was not clean.
         It can also occur of action is need to continue the
         operation for non-blocking BIOs. Call SSL_get_error()
         with the return value rrrreeeetttt to find out the reason.

SSSSEEEEEEEE AAAALLLLSSSSOOOO
     SSL_get_error(3), SSL_connect(3), SSL_shutdown(3), ssl(3),
     bio(3), SSL_set_connect_state(3), SSL_do_handshake(3),
     SSL_CTX_new(3)












































3/Jun/2003             Last change: 0.9.8o                      2