RabbitMQ server not coming up in FIPS enabled cluster #12278
-
Describe the bugWe are installing RabbitMQ on FIPS enabled cluster with {crypto, [{fips_mode, false}]} in advanced.config RabbitMQ logs
openssl version used - OpenSSL 3.0.7 1 Nov 2022 (Library: OpenSSL 3.0.7 1 Nov 2022) Expected behaviorAs {crypto, [{fips_mode, false}]} is configured, where I expect that rabbitmq(non-fips) will come up Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
Here it is mentioned that we dont have to compile erlang if we dont want to enable fips for rabbitmq alone on fips enabled env - erlang/otp#8797 |
Beta Was this translation helpful? Give feedback.
-
Please familiarize yourself with GitHub's features for formatting large amounts of text, OR save logs to a file and ATTACH the file to a discussion. Pasting large amounts of text is lazy and difficult to read. Team RabbitMQ's official community support policy states that we will not answer questions related to TLS or FIPS. Our expertise in those areas are reserved for RabbitMQ users who have paid for a support contract. In your case, the very least you could have done is provide your full configuration files. There is little we can do to assist you. Finally, I took the time to add |
Beta Was this translation helpful? Give feedback.
-
This is where the https://github.com/erlang/otp/blob/OTP-26.2.5/lib/crypto/c_src/evp.c#L52-L53 You can see that it has something to do with Erlang's interaction with OpenSSL. You state here:
Then don't add any settings to |
Beta Was this translation helpful? Give feedback.
This is where the
Reason for termination = error:{error,{"evp.c",136},"Can't make context"}
error originates:https://github.com/erlang/otp/blob/OTP-26.2.5/lib/crypto/c_src/evp.c#L52-L53
You can see that it has something to do with Erlang's interaction with OpenSSL.
You state here:
Then don't add any settings to
rabbitmq.conf
oradvanced.config
. RabbitMQ won't try to use FIPS.