SSL_accept.pod 2.3 KB
Newer Older
1 2 3 4
=pod

=head1 NAME

U
Ulf Möller 已提交
5
SSL_accept - wait for a TLS/SSL client to initiate a TLS/SSL handshake
6 7 8 9 10 11 12 13 14

=head1 SYNOPSIS

 #include <openssl/ssl.h>

 int SSL_accept(SSL *ssl);

=head1 DESCRIPTION

U
Ulf Möller 已提交
15
SSL_accept() waits for a TLS/SSL client to initiate the TLS/SSL handshake.
16
The communication channel must already have been set and assigned to the
17 18 19 20 21
B<ssl> by setting an underlying B<BIO>.

=head1 NOTES

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

U
Ulf Möller 已提交
23 24 25 26
If the underlying BIO is B<blocking>, 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 B<SSL_ERROR_WANT_READ/WRITE> and SSL_accept()
27 28
should be called again.

U
Ulf Möller 已提交
29
If the underlying BIO is B<non-blocking>, SSL_accept() will also return
30 31
when the underlying BIO could not satisfy the needs of SSL_accept()
to continue the handshake. In this case a call to SSL_get_error() with the
U
Ulf Möller 已提交
32 33
return value of SSL_accept() will yield B<SSL_ERROR_WANT_READ> or
B<SSL_ERROR_WANT_WRITE>. The calling process then must repeat the call after
34 35 36 37 38 39 40 41 42 43 44 45 46 47
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.

=head1 RETURN VALUES

The following return values can occur:

=over 4

=item 1

U
Ulf Möller 已提交
48
The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
49 50 51 52
established.

=item 0

U
Ulf Möller 已提交
53 54
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
55 56 57 58
return value B<ret> to find out the reason.

=item -1

U
Ulf Möller 已提交
59 60 61
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
62 63 64 65 66 67 68 69 70 71 72
for non-blocking BIOs. Call SSL_get_error() with the return value B<ret>
to find out the reason.

=back

=head1 SEE ALSO

L<SSL_get_error(3)|SSL_get_error(3)>, L<SSL_connect(3)|SSL_connect(3)>,
L<SSL_shutdown(3)|SSL_shutdown(3)>, L<ssl(3)|ssl(3)>, L<bio(3)|bio(3)>

=cut