-
Notifications
You must be signed in to change notification settings - Fork 3k
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
SSL version matching OTP 27.1.1 #8908
Comments
Yes alas I think it is a bug. I will fix it shortly. |
Will this solve your problem #8916 ? It feel like it should, I am looking into improving tests but am a bit swamped at the moment. |
Thank you @IngelaAndin ! |
Probably it doesn't help you much in writing a test case, but in this specific RabbitMQ test,
|
Thanks for the input, I realize now why my attempts of test case fail, and how it slipped through in the first place. The thing is that our own client will only send the version extension when TLS-1.3 is also supported. And I believe this also should be backported to TLS-1.2 clients among with other new TLS-1.3 features already backported. |
* ingela/ssl/fix-assert/GH-8908/OTP-19288: ssl: Fix version assertion
* ingela/ssl/fix-assert/GH-8908/OTP-19288: ssl: Fix version assertion
Is the
Version
in line 248 supposed to match theVersion
in line 245 in https://github.com/erlang/otp/blob/OTP-27.1.1/lib/ssl/src/tls_handshake.erl#L245-L248 ?I'm asking because
make -C deps/rabbitmq_mqtt ct-java t=v3
succeeds on RabbitMQ server
main
branch with OTP 27.1 but fails on OTP 27.1.1.When I add
{log_level, debug}
tossl_opttions
, then I see a badmatch as shownhere
Not sure if this is an OTP bug though?
The text was updated successfully, but these errors were encountered: