2001-08-17 22:32:38 +08:00
|
|
|
=pod
|
|
|
|
|
|
|
|
|
|
=head1 NAME
|
|
|
|
|
|
2016-05-04 00:55:00 +08:00
|
|
|
SSL_want, SSL_want_nothing, SSL_want_read, SSL_want_write, SSL_want_x509_lookup,
|
Add SSL_CTX early callback
Provide a callback interface that gives the application the ability
to adjust the nascent SSL object at the earliest stage of ClientHello
processing, immediately after extensions have been collected but
before they have been processed.
This is akin to BoringSSL's "select_certificate_cb" (though it is not
API compatible), and as the name indicates, one major use is to examine
the supplied server name indication and select what certificate to
present to the client. However, it can also be used to make more
sweeping configuration changes to the SSL object according to the
selected server identity and configuration. That may include adjusting
the permitted TLS versions, swapping out the SSL_CTX object (as is
traditionally done in a tlsext_servername_callback), changing the
server's cipher list, and more.
We also wish to allow an early callback to indicate that it needs to perform
additional work asynchronously and resume processing later. To that effect,
refactor the second half of tls_process_client_hello() into a subroutine to be
called at the post-processing stage (including the early callback itself), to
allow the callback to result in remaining in the same work stage for a later
call to succeed. This requires allocating for and storing the CLIENTHELLO_MSG
in the SSL object to be preserved across such calls, but the storage is
reclaimed after ClientHello processing finishes.
Information about the CliehtHello is available to the callback by means of
accessor functions that can only be used from the early callback. This allows
extensions to make use of the existing internal parsing machinery without
exposing structure internals (e.g., of PACKET), so that applications do not
have to write fragile parsing code.
Applications are encouraged to utilize an early callback and not use
a servername_callback, in order to avoid unexpected behavior that
occurs due to the relative order of processing between things like
session resumption and the historical servername callback.
Also tidy up nearby style by removing unnecessary braces around one-line
conditional bodies.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2279)
2017-01-24 07:03:16 +08:00
|
|
|
SSL_want_async, SSL_want_async_job, SSL_want_early - obtain state information
|
|
|
|
|
TLS/SSL I/O operation
|
2001-08-17 22:32:38 +08:00
|
|
|
|
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
|
|
|
|
|
|
#include <openssl/ssl.h>
|
|
|
|
|
|
2005-03-30 19:50:14 +08:00
|
|
|
int SSL_want(const SSL *ssl);
|
|
|
|
|
int SSL_want_nothing(const SSL *ssl);
|
|
|
|
|
int SSL_want_read(const SSL *ssl);
|
|
|
|
|
int SSL_want_write(const SSL *ssl);
|
|
|
|
|
int SSL_want_x509_lookup(const SSL *ssl);
|
2016-05-04 00:55:00 +08:00
|
|
|
int SSL_want_async(const SSL *ssl);
|
|
|
|
|
int SSL_want_async_job(const SSL *ssl);
|
Add SSL_CTX early callback
Provide a callback interface that gives the application the ability
to adjust the nascent SSL object at the earliest stage of ClientHello
processing, immediately after extensions have been collected but
before they have been processed.
This is akin to BoringSSL's "select_certificate_cb" (though it is not
API compatible), and as the name indicates, one major use is to examine
the supplied server name indication and select what certificate to
present to the client. However, it can also be used to make more
sweeping configuration changes to the SSL object according to the
selected server identity and configuration. That may include adjusting
the permitted TLS versions, swapping out the SSL_CTX object (as is
traditionally done in a tlsext_servername_callback), changing the
server's cipher list, and more.
We also wish to allow an early callback to indicate that it needs to perform
additional work asynchronously and resume processing later. To that effect,
refactor the second half of tls_process_client_hello() into a subroutine to be
called at the post-processing stage (including the early callback itself), to
allow the callback to result in remaining in the same work stage for a later
call to succeed. This requires allocating for and storing the CLIENTHELLO_MSG
in the SSL object to be preserved across such calls, but the storage is
reclaimed after ClientHello processing finishes.
Information about the CliehtHello is available to the callback by means of
accessor functions that can only be used from the early callback. This allows
extensions to make use of the existing internal parsing machinery without
exposing structure internals (e.g., of PACKET), so that applications do not
have to write fragile parsing code.
Applications are encouraged to utilize an early callback and not use
a servername_callback, in order to avoid unexpected behavior that
occurs due to the relative order of processing between things like
session resumption and the historical servername callback.
Also tidy up nearby style by removing unnecessary braces around one-line
conditional bodies.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2279)
2017-01-24 07:03:16 +08:00
|
|
|
int SSL_want_early(const SSL *ssl);
|
2001-08-17 22:32:38 +08:00
|
|
|
|
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
|
|
|
|
|
SSL_want() returns state information for the SSL object B<ssl>.
|
|
|
|
|
|
|
|
|
|
The other SSL_want_*() calls are shortcuts for the possible states returned
|
|
|
|
|
by SSL_want().
|
|
|
|
|
|
|
|
|
|
=head1 NOTES
|
|
|
|
|
|
|
|
|
|
SSL_want() examines the internal state information of the SSL object. Its
|
2015-08-18 03:21:33 +08:00
|
|
|
return values are similar to that of L<SSL_get_error(3)>.
|
|
|
|
|
Unlike L<SSL_get_error(3)>, which also evaluates the
|
2001-08-17 22:32:38 +08:00
|
|
|
error queue, the results are obtained by examining an internal state flag
|
|
|
|
|
only. The information must therefore only be used for normal operation under
|
|
|
|
|
non-blocking I/O. Error conditions are not handled and must be treated
|
2015-08-18 03:21:33 +08:00
|
|
|
using L<SSL_get_error(3)>.
|
2001-08-17 22:32:38 +08:00
|
|
|
|
|
|
|
|
The result returned by SSL_want() should always be consistent with
|
2015-08-18 03:21:33 +08:00
|
|
|
the result of L<SSL_get_error(3)>.
|
2001-08-17 22:32:38 +08:00
|
|
|
|
|
|
|
|
=head1 RETURN VALUES
|
|
|
|
|
|
|
|
|
|
The following return values can currently occur for SSL_want():
|
|
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
|
|
|
|
=item SSL_NOTHING
|
|
|
|
|
|
|
|
|
|
There is no data to be written or to be read.
|
|
|
|
|
|
|
|
|
|
=item SSL_WRITING
|
|
|
|
|
|
|
|
|
|
There are data in the SSL buffer that must be written to the underlying
|
|
|
|
|
B<BIO> layer in order to complete the actual SSL_*() operation.
|
2015-08-18 03:21:33 +08:00
|
|
|
A call to L<SSL_get_error(3)> should return
|
2001-08-17 22:32:38 +08:00
|
|
|
SSL_ERROR_WANT_WRITE.
|
|
|
|
|
|
|
|
|
|
=item SSL_READING
|
|
|
|
|
|
|
|
|
|
More data must be read from the underlying B<BIO> layer in order to
|
|
|
|
|
complete the actual SSL_*() operation.
|
2015-08-18 03:21:33 +08:00
|
|
|
A call to L<SSL_get_error(3)> should return
|
2001-08-17 22:32:38 +08:00
|
|
|
SSL_ERROR_WANT_READ.
|
|
|
|
|
|
|
|
|
|
=item SSL_X509_LOOKUP
|
|
|
|
|
|
|
|
|
|
The operation did not complete because an application callback set by
|
|
|
|
|
SSL_CTX_set_client_cert_cb() has asked to be called again.
|
2015-08-18 03:21:33 +08:00
|
|
|
A call to L<SSL_get_error(3)> should return
|
2001-08-17 22:32:38 +08:00
|
|
|
SSL_ERROR_WANT_X509_LOOKUP.
|
|
|
|
|
|
2016-05-04 00:55:00 +08:00
|
|
|
=item SSL_ASYNC_PAUSED
|
|
|
|
|
|
|
|
|
|
An asynchronous operation partially completed and was then paused. See
|
|
|
|
|
L<SSL_get_all_async_fds(3)>. A call to L<SSL_get_error(3)> should return
|
|
|
|
|
SSL_ERROR_WANT_ASYNC.
|
|
|
|
|
|
|
|
|
|
=item SSL_ASYNC_NO_JOBS
|
|
|
|
|
|
|
|
|
|
The asynchronous job could not be started because there were no async jobs
|
|
|
|
|
available in the pool (see ASYNC_init_thread(3)). A call to L<SSL_get_error(3)>
|
|
|
|
|
should return SSL_ERROR_WANT_ASYNC_JOB.
|
|
|
|
|
|
Add SSL_CTX early callback
Provide a callback interface that gives the application the ability
to adjust the nascent SSL object at the earliest stage of ClientHello
processing, immediately after extensions have been collected but
before they have been processed.
This is akin to BoringSSL's "select_certificate_cb" (though it is not
API compatible), and as the name indicates, one major use is to examine
the supplied server name indication and select what certificate to
present to the client. However, it can also be used to make more
sweeping configuration changes to the SSL object according to the
selected server identity and configuration. That may include adjusting
the permitted TLS versions, swapping out the SSL_CTX object (as is
traditionally done in a tlsext_servername_callback), changing the
server's cipher list, and more.
We also wish to allow an early callback to indicate that it needs to perform
additional work asynchronously and resume processing later. To that effect,
refactor the second half of tls_process_client_hello() into a subroutine to be
called at the post-processing stage (including the early callback itself), to
allow the callback to result in remaining in the same work stage for a later
call to succeed. This requires allocating for and storing the CLIENTHELLO_MSG
in the SSL object to be preserved across such calls, but the storage is
reclaimed after ClientHello processing finishes.
Information about the CliehtHello is available to the callback by means of
accessor functions that can only be used from the early callback. This allows
extensions to make use of the existing internal parsing machinery without
exposing structure internals (e.g., of PACKET), so that applications do not
have to write fragile parsing code.
Applications are encouraged to utilize an early callback and not use
a servername_callback, in order to avoid unexpected behavior that
occurs due to the relative order of processing between things like
session resumption and the historical servername callback.
Also tidy up nearby style by removing unnecessary braces around one-line
conditional bodies.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2279)
2017-01-24 07:03:16 +08:00
|
|
|
=item SSL_EARLY_WORK
|
|
|
|
|
|
|
|
|
|
The operation did not complete because an application callback set by
|
|
|
|
|
SSL_CTX_set_early_cb() has asked to be called again.
|
|
|
|
|
A call to L<SSL_get_error(3)> should return
|
|
|
|
|
SSL_ERROR_WANT_EARLY.
|
|
|
|
|
|
2001-08-17 22:32:38 +08:00
|
|
|
=back
|
|
|
|
|
|
2016-05-04 00:55:00 +08:00
|
|
|
SSL_want_nothing(), SSL_want_read(), SSL_want_write(), SSL_want_x509_lookup(),
|
Add SSL_CTX early callback
Provide a callback interface that gives the application the ability
to adjust the nascent SSL object at the earliest stage of ClientHello
processing, immediately after extensions have been collected but
before they have been processed.
This is akin to BoringSSL's "select_certificate_cb" (though it is not
API compatible), and as the name indicates, one major use is to examine
the supplied server name indication and select what certificate to
present to the client. However, it can also be used to make more
sweeping configuration changes to the SSL object according to the
selected server identity and configuration. That may include adjusting
the permitted TLS versions, swapping out the SSL_CTX object (as is
traditionally done in a tlsext_servername_callback), changing the
server's cipher list, and more.
We also wish to allow an early callback to indicate that it needs to perform
additional work asynchronously and resume processing later. To that effect,
refactor the second half of tls_process_client_hello() into a subroutine to be
called at the post-processing stage (including the early callback itself), to
allow the callback to result in remaining in the same work stage for a later
call to succeed. This requires allocating for and storing the CLIENTHELLO_MSG
in the SSL object to be preserved across such calls, but the storage is
reclaimed after ClientHello processing finishes.
Information about the CliehtHello is available to the callback by means of
accessor functions that can only be used from the early callback. This allows
extensions to make use of the existing internal parsing machinery without
exposing structure internals (e.g., of PACKET), so that applications do not
have to write fragile parsing code.
Applications are encouraged to utilize an early callback and not use
a servername_callback, in order to avoid unexpected behavior that
occurs due to the relative order of processing between things like
session resumption and the historical servername callback.
Also tidy up nearby style by removing unnecessary braces around one-line
conditional bodies.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2279)
2017-01-24 07:03:16 +08:00
|
|
|
SSL_want_async(), SSL_want_async_job(), and SSL_want_early() return 1, when
|
|
|
|
|
the corresponding condition is true or 0 otherwise.
|
2001-08-17 22:32:38 +08:00
|
|
|
|
|
|
|
|
=head1 SEE ALSO
|
|
|
|
|
|
2017-03-02 23:07:21 +08:00
|
|
|
L<ssl(7)>, L<SSL_get_error(3)>
|
2001-08-17 22:32:38 +08:00
|
|
|
|
Add SSL_CTX early callback
Provide a callback interface that gives the application the ability
to adjust the nascent SSL object at the earliest stage of ClientHello
processing, immediately after extensions have been collected but
before they have been processed.
This is akin to BoringSSL's "select_certificate_cb" (though it is not
API compatible), and as the name indicates, one major use is to examine
the supplied server name indication and select what certificate to
present to the client. However, it can also be used to make more
sweeping configuration changes to the SSL object according to the
selected server identity and configuration. That may include adjusting
the permitted TLS versions, swapping out the SSL_CTX object (as is
traditionally done in a tlsext_servername_callback), changing the
server's cipher list, and more.
We also wish to allow an early callback to indicate that it needs to perform
additional work asynchronously and resume processing later. To that effect,
refactor the second half of tls_process_client_hello() into a subroutine to be
called at the post-processing stage (including the early callback itself), to
allow the callback to result in remaining in the same work stage for a later
call to succeed. This requires allocating for and storing the CLIENTHELLO_MSG
in the SSL object to be preserved across such calls, but the storage is
reclaimed after ClientHello processing finishes.
Information about the CliehtHello is available to the callback by means of
accessor functions that can only be used from the early callback. This allows
extensions to make use of the existing internal parsing machinery without
exposing structure internals (e.g., of PACKET), so that applications do not
have to write fragile parsing code.
Applications are encouraged to utilize an early callback and not use
a servername_callback, in order to avoid unexpected behavior that
occurs due to the relative order of processing between things like
session resumption and the historical servername callback.
Also tidy up nearby style by removing unnecessary braces around one-line
conditional bodies.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2279)
2017-01-24 07:03:16 +08:00
|
|
|
=head1 HISTORY
|
|
|
|
|
|
|
|
|
|
SSL_want_early() and SSL_EARLY_WORK were added in OpenSSL 1.1.1.
|
|
|
|
|
|
2016-05-18 23:44:05 +08:00
|
|
|
=head1 COPYRIGHT
|
|
|
|
|
|
Add SSL_CTX early callback
Provide a callback interface that gives the application the ability
to adjust the nascent SSL object at the earliest stage of ClientHello
processing, immediately after extensions have been collected but
before they have been processed.
This is akin to BoringSSL's "select_certificate_cb" (though it is not
API compatible), and as the name indicates, one major use is to examine
the supplied server name indication and select what certificate to
present to the client. However, it can also be used to make more
sweeping configuration changes to the SSL object according to the
selected server identity and configuration. That may include adjusting
the permitted TLS versions, swapping out the SSL_CTX object (as is
traditionally done in a tlsext_servername_callback), changing the
server's cipher list, and more.
We also wish to allow an early callback to indicate that it needs to perform
additional work asynchronously and resume processing later. To that effect,
refactor the second half of tls_process_client_hello() into a subroutine to be
called at the post-processing stage (including the early callback itself), to
allow the callback to result in remaining in the same work stage for a later
call to succeed. This requires allocating for and storing the CLIENTHELLO_MSG
in the SSL object to be preserved across such calls, but the storage is
reclaimed after ClientHello processing finishes.
Information about the CliehtHello is available to the callback by means of
accessor functions that can only be used from the early callback. This allows
extensions to make use of the existing internal parsing machinery without
exposing structure internals (e.g., of PACKET), so that applications do not
have to write fragile parsing code.
Applications are encouraged to utilize an early callback and not use
a servername_callback, in order to avoid unexpected behavior that
occurs due to the relative order of processing between things like
session resumption and the historical servername callback.
Also tidy up nearby style by removing unnecessary braces around one-line
conditional bodies.
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Richard Levitte <levitte@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2279)
2017-01-24 07:03:16 +08:00
|
|
|
Copyright 2001-2017 The OpenSSL Project Authors. All Rights Reserved.
|
2016-05-18 23:44:05 +08:00
|
|
|
|
|
|
|
|
Licensed under the OpenSSL license (the "License"). You may not use
|
|
|
|
|
this file except in compliance with the License. You can obtain a copy
|
|
|
|
|
in the file LICENSE in the source distribution or at
|
|
|
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
|
|
|
|
|
|
=cut
|
