@@ -2596,11 +2596,6 @@ static const multi_client_connect_handler client_connect_handlers[] = {
static void
multi_connection_established(struct multi_context *m, struct multi_instance *mi)
{
- if (tls_authentication_status(mi->context.c2.tls_multi) != TLS_AUTHENTICATION_SUCCEEDED)
- {
- return;
- }
-
/* We are only called for the CAS_PENDING_x states, so we
* can ignore other states here */
bool from_deferred = (mi->context.c2.tls_multi->multi_state != CAS_PENDING);
@@ -2810,7 +2810,7 @@ tls_process(struct tls_multi *multi,
if (session->opt->mode == MODE_SERVER)
{
/* On a server we continue with running connect scripts next */
- multi->multi_state = CAS_PENDING;
+ multi->multi_state = CAS_WAITING_AUTH;
}
else
{
@@ -3136,6 +3136,13 @@ tls_multi_process(struct tls_multi *multi,
enum tls_auth_status tas = tls_authentication_status(multi);
+ /* If we have successfully authenticated and are still waiting for the authentication to finish
+ * move the state machine for the multi context forward */
+ if (multi->multi_state == CAS_WAITING_AUTH && tas == TLS_AUTHENTICATION_SUCCEEDED)
+ {
+ multi->multi_state = CAS_PENDING;
+ }
+
/*
* If lame duck session expires, kill it.
*/
@@ -511,6 +511,7 @@ struct tls_session
* connect scripts/plugins */
enum multi_status {
CAS_NOT_CONNECTED,
+ CAS_WAITING_AUTH, /**< TLS connection established but deferred auth not finished */
CAS_PENDING,
CAS_PENDING_DEFERRED,
CAS_PENDING_DEFERRED_PARTIAL, /**< at least handler succeeded, no result yet*/
Previously we relied on checking tls_authentication_status to check wether to determine if the context auth state is actually valid or not. This patch eliminates that check by introducing waiting on the authentication as extra state in the context auth, state machine. Signed-off-by: Arne Schwabe <arne@rfc2549.org> --- src/openvpn/multi.c | 5 ----- src/openvpn/ssl.c | 9 ++++++++- src/openvpn/ssl_common.h | 1 + 3 files changed, 9 insertions(+), 6 deletions(-)