You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This new return value, MBEDTLS_ERR_SSL_RECEIVED_NEW_SESSION_TICKET, will be propagated to public API, such as mbedtls_ssl_read, mbedtls_ssl_handshake and mbedtls_ssl_write. The client need add code to handle new return code.
In some cases with async io, mbedtls_ssl_write will return MBEDTLS_ERR_SSL_RECEIVED_NEW_SESSION_TICKET. This happens when the state transits to MBEDTLS_SSL_CLIENT_NEW_SESSION_TICKET, and mbedtls_ssl_write is called immediate after it.
The text was updated successfully, but these errors were encountered:
Suggested enhancement
Should we consider the callback style API to report a new session ticket is received by the client?
Justification
OpenSSL uses SSL_CTX_sess_set_new_cb to report a new session ticket.
In mbedtls TLS 1.3, we report it via return code, MBEDTLS_ERR_SSL_RECEIVED_NEW_SESSION_TICKET. There are couple of limitations in current approach.
MBEDTLS_ERR_SSL_RECEIVED_NEW_SESSION_TICKET
, will be propagated to public API, such asmbedtls_ssl_read
,mbedtls_ssl_handshake
andmbedtls_ssl_write
. The client need add code to handle new return code.mbedtls_ssl_write
will returnMBEDTLS_ERR_SSL_RECEIVED_NEW_SESSION_TICKET
. This happens when the state transits to MBEDTLS_SSL_CLIENT_NEW_SESSION_TICKET, andmbedtls_ssl_write
is called immediate after it.The text was updated successfully, but these errors were encountered: