Skip to content

remove fail_if_no_peer_cert#1933

Merged
lukebakken merged 1 commit intorabbitmq:mainfrom
womblep:patch-1
May 24, 2024
Merged

remove fail_if_no_peer_cert#1933
lukebakken merged 1 commit intorabbitmq:mainfrom
womblep:patch-1

Conversation

@womblep
Copy link
Copy Markdown
Contributor

@womblep womblep commented May 24, 2024

Remove fail_if_no_peer_cert from amqp_client options as it is no longer valid with Erlang 26 and will stop the connection from working

Remove fail_if_no_peer_cert from amqp_client options as it is no longer valid with Erlang 26 and will stop the connection from working
@pivotal-cla
Copy link
Copy Markdown

@womblep Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-cla
Copy link
Copy Markdown

@womblep Thank you for signing the Contributor License Agreement!

@lukebakken
Copy link
Copy Markdown
Collaborator

Thanks!

@lukebakken lukebakken merged commit 73c0ef0 into rabbitmq:main May 24, 2024
@michaelklishin
Copy link
Copy Markdown
Contributor

This is a new parameter check in Erlang 26's TLS implementation, as far as I can tell. In other words, it has gone unnoticed because very likley it's a valid combination of settings on Erlang 25.

@michaelklishin
Copy link
Copy Markdown
Contributor

michaelklishin commented Jul 29, 2024

Note: this was not backported to the 3.13.x version of the docs.

Corrected in 2ac6c0f.

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.

4 participants