| Summary: | net-im/ejabberd crashes with openssl+zlib | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Vick Khera <vivek> |
| Component: | Individual Port(s) | Assignee: | Ashish SHUKLA <ashish> |
| Status: | Closed Not Accepted | ||
| Severity: | Affects Only Me | CC: | cs |
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Vick Khera
2013-09-10 17:30:01 UTC
Responsible Changed From-To: freebsd-ports-bugs->ashish Over to maintainer. Hi Vivek, This is a known issue[1] from quite sometime. I'm not sure about the fix either, though the workaround you already posted. Probably a bug needs to be filed upstream, if not already in all these years. I can file one by the end of the week, if you've not already reported it upstream. References: [1] http://lists.jabber.ru/pipermail/ejabberd/2007-March/002604.html Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs Wow. Thanks for the followup. I searched google but nothing like this came up. I'm shocked that 6 years later it sill crashes like that! I don't think it is such a big deal, since current security thinking is that compression on encrypted streams is a bad idea anyway, at least for HTTPS. Hi, Filed an upstream bug report EJAB-1663[1]. References: [1] https://support.process-one.net/browse/EJAB-1663 -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 Sent from my Emacs Is this PR still relevant? (In reply to Carlo Strub from comment #5) > Is this PR still relevant? It's still not fixed AFAIK, and is being tracked upstream. Ashish Closing PR because it was reported upstream. |