Bug 212880

Summary:	lang/erlang: Usage with RabbitMQ breaks SSL/TLS handshake with .NET clients
Product:	Ports & Packages	Reporter:	Lucas Holt <luke>
Component:	Individual Port(s)	Assignee:	Jimmy Olgeni <olgeni>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	olgeni, w.schwarzenfeld
Priority:	---	Keywords:	needs-qa, regression
Version:	Latest	Flags:	vlad-fbsd: maintainer-feedback? (olgeni)
Hardware:	Any
OS:	Any

Description Lucas Holt 2016-09-21 14:32:44 UTC

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?

Comment 1 Lucas Holt 2016-09-25 20:10:28 UTC

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.

Comment 2 Jimmy Olgeni freebsd_committer

2016-09-26 08:08:13 UTC

(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)

Comment 3 Jimmy Olgeni freebsd_committer

2016-09-29 15:05:01 UTC

19.1.1 apparently has a fix - looking into it

Comment 4 Walter Schwarzenfeld 2018-01-14 00:19:08 UTC

Is this still relevant?

Comment 5 Lucas Holt 2018-01-14 15:29:24 UTC

This has been fixed.