You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is a limitation of Eventmachine so feel free to let me know if so, but currently there is no way to send the client certificate to the peer for verification when using an SSL connection.
You end up seeing something like this:
Apr 2 13:51:05 ubuntu stunnel: LOG5[21813:3073223488]: Service amqp-server accepted connection from 192.168.1.10:44798
Apr 2 13:51:05 ubuntu stunnel: LOG3[21813:3073223488]: SSL_accept: 140890C7: error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate
Apr 2 13:51:05 ubuntu stunnel: LOG5[21813:3073223488]: Connection reset: 0 bytes sent to SSL, 0 bytes sent to socket
On a somewhat related note, if you enable :verify_peer: true in the SSL configuration hash, this also fails as amq-client does not implement the ssl_verify_peer() method that Eventmachine will call on the EventMachine::Connection class. This causes the ruby-amqp end to disconnect early right now, I guess because nothing is handling the verification.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is a limitation of Eventmachine so feel free to let me know if so, but currently there is no way to send the client certificate to the peer for verification when using an SSL connection.
You end up seeing something like this:
On a somewhat related note, if you enable
:verify_peer: true
in the SSL configuration hash, this also fails as amq-client does not implement thessl_verify_peer()
method that Eventmachine will call on theEventMachine::Connection
class. This causes the ruby-amqp end to disconnect early right now, I guess because nothing is handling the verification.The text was updated successfully, but these errors were encountered: