Ingela Andin
Ingela Andin
@Maria-12648430, @rickard-green I think it sounds like a good idea. We should prioritize when people are back from summer vacation.
@juhlig Status is that is in the queue of things we are trying to care about, but struggling to find time for. At last we managed to find enough time...
Well to make a long story short. Extensions marked critical must be verified. If they are not marked critical and they do not have to be verified but could be....
@loftkey So this was a little more involved then anticipated, but now finally I have shaped up my PR #8840 so that you can try it out. I still need...
It was released in [OTP 27.1.3](https://github.com/erlang/otp/releases/tag/OTP-27.1.3) [OTP 26.2.5.6](https://github.com/erlang/otp/releases/tag/OTP-26.2.5.6) and [OTP 25.3.2.16](https://github.com/erlang/otp/releases/tag/OTP-25.3.2.16)
If your problem is related to the end entity certificate and not to a ca-certificate I think you should open a new issue. And in that case I guess it...
Well the problem is that the server you are connecting to is not adhering to the spec on how middlebox mode should behave. Probably the easiest fix is to disable...
It is a ssl_option to be set on the client.
You could try verifying your options in an erlang shell calling ssl:connect/3 first and then supply them via appropriate Rabbit configuration.
It is probably not working with FIPS, as FIPS does not allow an algorithm that is checked for when checking for TLS-1.3 support. I have made a change for that...