rabbitmq management plugins support with TLSV1.3 #3757
Replies: 4 comments
-
I will convert this issue to a GitHub discussion. Currently GitHub will automatically close and lock the issue even though your question will be transferred and responded to elsewhere. This is to let you know that we do not intend to ignore this but this is how the current GitHub conversion mechanism makes it seem for the users :( |
Beta Was this translation helpful? Give feedback.
-
The same set of settings (namely cipher suites) under |
Beta Was this translation helpful? Give feedback.
-
In a discussion with @lhoguin we have noticed that Cowboy, the HTTP server used by this API, may be injecting some options by default that won't be compatible with TLSv1.3. So when TLSv1.3 is enabled exclusively, Cowboy may need to be extra defensive in future versions. Otherwise everything should be ready to use TLSv1.3 with any of the protocols supported, as long as there are no option conflicts with earlier versions. |
Beta Was this translation helpful? Give feedback.
-
This Erlang 24.1 bug is worth mentioning as our team has hit it several times with various protocols. It seems to have been fixed in |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Documentations refer to tlsv1.3 for rabbitmq server only. Is TLSv1.3 officially supported for the management plugin api of the rabbitmq server ?
Beta Was this translation helpful? Give feedback.
All reactions