The combination of RabbitMQ 3.6.5 and erlang-19.0.7,3 as well as 19.0.6 have broken TLS/SSL handshakes with .NET clients using the latest 3.6.5 library for .NET/C#. This doesn't affect Java and must be a bug or change in erlang. The previous erlang version from r420247 works with .NET. Would it be possible to add a erlang18 port that can be used with rabbit mq and/or a warning message about this to the port?
I wanted to note that I ended up opening a bug with the erlang folks on this too. https://bugs.erlang.org/browse/ERL-259 I'm hoping there will be an upstream fix for this eventually.
(In reply to Lucas Holt from comment #1) Hi, are you able to test the proposed patch? (not sure if this is related to other SSL client issues)
19.1.1 apparently has a fix - looking into it
Is this still relevant?
This has been fixed.