The tls13 client may send two change cipher spec(ccs) messages when MBEDTLS_SSL_TLS13_COMPATIBILITY_MODE is on. One is right after client hello and another is before server finish. The first one seems redundant.
Maybe we need a flag to bookkeeping if ccs is sent or not.
System information
This issue doesn't happen in development branch. (i.e. MVP). It happens in the tls13-prototype branch.
Mbed TLS version (number or commit id):
Operating system and version:
Configuration (if not default, please attach mbedtls_config.h):
Compiler and options (if you used a pre-built binary, please indicate how you obtained it):
Additional environment information:
Summary
The tls13 client may send two change cipher spec(ccs) messages when
MBEDTLS_SSL_TLS13_COMPATIBILITY_MODE
is on. One is right after client hello and another is before server finish. The first one seems redundant. Maybe we need a flag to bookkeeping if ccs is sent or not.System information
This issue doesn't happen in development branch. (i.e. MVP). It happens in the tls13-prototype branch.
Mbed TLS version (number or commit id): Operating system and version: Configuration (if not default, please attach
mbedtls_config.h
): Compiler and options (if you used a pre-built binary, please indicate how you obtained it): Additional environment information:Expected behavior
Only one ccs should be sent.
Actual behavior
Two ccs may be sent.
Steps to reproduce
Check
write change cipher spec
in the logAdditional information