Sensu clients using rabbitmq + TLS should verify the server certificate

[Fitzsimmons]

Current Behavior

The AMQP client used by the sensu-client doesn't verify the server's certificate, making it trivial to carry out a man in the middle attack against the TLS connection. It defeats the purpose of using TLS if the authentication is disabled.

Expected Behavior

The AMQP client verifies the connection domain name against the server certificate's Subject Alternative Names or Common Name (although CN is now deprecated). The connection is aborted if the domain name does not match or the issuer of the server's cert is not trusted by the OS's local store or a user-configured CA.

Possible Solution

Implement the ssl_verify_peer method for the AMQP gem.

[Fitzsimmons]

Yup this is a dupe, sorry