-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Fail to complete TLS handshake to httpstat.us by TLS1.3 #8669
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for the report. The random bytes in the second ClientHello should indeed be the same as the ones in the first ClientHello. We have to fix that. The proposed patch seems to go on the right direction but probably misses some "#if defined(MBEDTLS_SSL_PROTO_TLS1_3)" guard as the |
Thanks for the suggestion. Will you create a PR or I should do it? |
If you would like to create a PR it would be welcome |
* In TLS 1.3 clients, fix an interoperability problem due to the client generating a new random after a HelloRetryRequest. Fixes Mbed-TLS#8669. Signed-off-by: BensonLiou <[email protected]>
Summary
Received "protocol version (70)" error from server while connecting by ssl_client2
System information
Mbed TLS version (number or commit id):
593e9cb
Operating system and version:
WLS2 ubuntu (5.15.90.1-microsoft-standard-WSL2)
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):
gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
Additional environment information:
NA
Expected behavior
Complete the SSL handshake
Actual behavior
Received "protocol version (70)" error from server
Steps to reproduce
execute
programs/ssl/ssl_client2 server_name=httpstat.us server_port=443 auth_mode=none force_version=tls13
Additional information
There is no issue on openssl. I could connect to same server by
openssl s_client -connect httpstat.us:443 -tls1_3
I found the random number is different in two ClientHello. According to RFC8446, two ClientHello have to be same.
I could fix this issue with following patch
Please check if this patch is good enough
The text was updated successfully, but these errors were encountered: