Skip to content
This repository has been archived by the owner on Sep 11, 2022. It is now read-only.

Client connections to RabbitMQ do not verify the server's certificate or hostname #241

Open
mdrozdo opened this issue Oct 4, 2018 · 1 comment

Comments

@mdrozdo
Copy link

mdrozdo commented Oct 4, 2018

Originally reported under the sensu repo. You can see sensu/sensu#1310 for details.

The callback functionality in eventmachine for verifying the certificate (it's not done automatically) isn't being used by ruby-amqp, so client connections to RabbitMQ do not verify the server's certificate or hostname.

We've verified that when running the client on Windows, any server certificate is automatically accepted without verifying the CA.

@michaelklishin
Copy link
Member

This client has been out of development for years. Sensu really should switch to Bunny.

Assuming that EventMachine peer verification isn't too different from what most TLS implementations do it should be easy to add.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants