Skip to content

Conversation

joakim-tjernlund
Copy link

TLS 1.3 server may choose to issue new session ticket in the middle of active connection. This will cause next mbedtls_ssl_read() or mbedtls_ssl_write() to return MBEDTLS_ERR_SSL_RECEIVED_NEW_SESSION_TICKET. This is not a real error, rather notification to the application to save session ticket for later use. As TLS reconnection is out of scope at this point we can safely ignore it and retry operation.

Please refer to mbedtls/programs/ssl/ssl_client2.c for session ticket handling.

TLS 1.3 server may choose to issue new session ticket in the middle
of active connection. This will cause next mbedtls_ssl_read() or
mbedtls_ssl_write() to return MBEDTLS_ERR_SSL_RECEIVED_NEW_SESSION_TICKET.
This is not a real error, rather notification to the application
to save session ticket for later use. As TLS reconnection is out of
scope at this point we can safely ignore it and retry operation.

Please refer to mbedtls/programs/ssl/ssl_client2.c for session ticket
handling.

Signed-off-by: Joakim Tjernlund <joakim.tjernlund@infinera.com>
@joakim-tjernlund
Copy link
Author

Ping?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant