Summary: | net-im/ejabberd: Does not start when built against LibreSSL | ||||||
---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Romain Tartière <romain> | ||||
Component: | Individual Port(s) | Assignee: | Ashish SHUKLA <ashish> | ||||
Status: | Closed FIXED | ||||||
Severity: | Affects Only Me | CC: | clukas, romain | ||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(ashish) |
||||
Version: | Latest | ||||||
Hardware: | Any | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Romain Tartière
![]() ![]() D'oh, a fix was committed a few days ago: https://github.com/processone/fast_tls/commit/a2b2154d11280becbf3077e62f7b5621d52b54fd There was no release including this fix yet, but I am currently running on top of master and everything looks fine! (In reply to Romain Tartière from comment #1) Let me try updating ejabberd to 17.11 including that fast_tls diff. Thanks for letting me know. Created attachment 189012 [details]
Update diff to 17.11
- Update to 17.11
- Add a diff from master to make it work with LibreSSL
- Add a diff from master to fix a bug in ejabberd_pix module
- Fix kqueue implementation in fs dependency module (need to be pushed upstream)
(In reply to Romain Tartière from comment #1) Hi, Could you try the diff in attachment 189012 [details] to see if it works for you ? Also, if you can provide feedback with their LE support[1], that will be great. I'm traveling, and will commit it around December 27, or so. [1] https://github.com/processone/ejabberd/pull/1959 Thanks! Hi! I have just recompiled all my ports with an up-to-date ports tree and your patch and updated everything. It looks like ejabberd is performing well :-) - Users can authenticate against the LDAP server; - Users can communicate with each other. So for me, everything is fine, thanks! Regarding your request concerning Let's Encrypt support, I do not currently use this. Have you something specific in mind in respect to this? (In reply to Romain Tartière from comment #5) For some reason, I thought you use it. If you don't use it, or don't have a use-case, then no worries. Thank you for the confirmation. I'll commit it, when I get back. Oh, okay :-) I didn't know about this let's encrypt module module, and it would definitively make sense in my setup, so be assured I will have a look at this in at some point in the future (after new year holiday). Thank you for the pointer! A commit references this bug: Author: ashish Date: Tue Dec 26 21:28:37 UTC 2017 New revision: 457315 URL: https://svnweb.freebsd.org/changeset/ports/457315 Log: - Update to 17.11 - Add a fix from upstream to make it work with LibreSSL[1] - Add a bug fix from upstream w.r.t. ejabberd_pix module - Add a fix for kqueue implementation in 'fs' dependency module - Remove FreeBSD sed workaround PR: 224320 [1] Submitted by: romain [1] Changes: head/net-im/ejabberd/Makefile head/net-im/ejabberd/distinfo head/net-im/ejabberd/files/patch-Makefile.in head/net-im/ejabberd/files/patch-deps_fast__tls_c__src_fast__tls.c head/net-im/ejabberd/files/patch-deps_fs_c__src_bsd_main.c head/net-im/ejabberd/files/patch-deps_fs_src_sys_kqueue.erl head/net-im/ejabberd/files/patch-ejabberdctl.template head/net-im/ejabberd/files/patch-src_ejabberd__pkix.erl head/net-im/ejabberd/files/pkg-install.in head/net-im/ejabberd/pkg-plist (In reply to Romain Tartière from comment #7) I have tested it with one of my domain names, and it seems to work as expected (at least initial certificate procurement part). Also thanks, committed the update. |