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
{{ message }}
Repository navigation
--tls-cipher-list=DEFAULT@SECLEVEL=0 doesn't compatible with tls1.3 #43419
I try to set --tls-cipher-list=DEFAULT@SECLEVEL=0, which can connect with tls1.0 , but can not connect with tls1.3.
but, if I use the openssl3.0, and set the SECLEVEL=0, it works well both connect 1.0 and 1.3.
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
how to set the option that make it can work same as openssl, that can connect both 1.0 and 1.3. I knows 1.0 and 1.1 has been deprecated.
error:0A0000B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available:c:\ws\deps\openssl\openssl\ssl\statem\statem_clnt.c:3749:No ciphers enabled for max supported SSL/TLS version
changed the title [-]--tls-cipher-list=DEFAULT@SECLEVEL=0 doesn't compatible with tsl1.3[/-][+]--tls-cipher-list=DEFAULT@SECLEVEL=0 doesn't compatible with tls1.3[/+]on Jun 15, 2022
This will have to be merged first and then released in 18.x. It will appear in the changes and also in the pull request when it gets merged for next 18.x release or possibly backported to older versions. I guess a week or two at least before 18.x
Activity
AdamMajer commentedon Jun 14, 2022
Another test case is using crypto-policies ciphers,
The root cause is we seem to assume that there are no default cipher suites
[-]--tls-cipher-list=DEFAULT@SECLEVEL=0 doesn't compatible with tsl1.3[/-][+]--tls-cipher-list=DEFAULT@SECLEVEL=0 doesn't compatible with tls1.3[/+]benzhuo commentedon Jun 15, 2022
@AdamMajer Thanks very much. when the fix will be released ?
Now, I am using a workaround that set --openssl-config=openssl.cnf
AdamMajer commentedon Jun 20, 2022
This will have to be merged first and then released in 18.x. It will appear in the changes and also in the pull request when it gets merged for next 18.x release or possibly backported to older versions. I guess a week or two at least before 18.x
crypto: don't disable TLS 1.3 without suites
crypto: don't disable TLS 1.3 without suites
crypto: don't disable TLS 1.3 without suites
crypto: don't disable TLS 1.3 without suites
crypto: don't disable TLS 1.3 without suites
crypto: don't disable TLS 1.3 without suites