-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade EJABBERD package from version 2 to the current version which is 16.01 #2095
Comments
The situation is slightly less alarming ;) Ejabberd v2's codebase is not the same codebase as subsequent versions. Support for v2 continued while the new codebase, from which v16 stems, became mature. I have looked into packaging a current Ejabberd version, but it's a huge pain and a lot of work. There are a lot of dependencies included in the main package, and each has to be split off into its own package for cross-compiling. Very slow going... |
Thanks for the reply. That does sound better than I had feared. It does look like there are a couple of vulns that people should be aware of related to the ssl code just getting old. |
I'm joining to this request, also looking for an update of eJabberd Server package for ours Synology... Regards, |
I would be also happy to see latest release of ejabberd on Synology. Hope someone will be able to get through the painstaking job :) |
@teihoo, @oli-oli, @askpatrickw |
Sweet! Thank you for this, I'll try setting it up this weekend. |
@teihoo did you have a chance to test this? |
I did it installed fine and it works to login. I had issues with setting up admin account and further configuration, as it was hitting me with login prompt on virtual servers and admin login didn't work. I need a bit more time trying to get it setup. |
The ejabberd package is version 2, but the current version is 16.
I can only imagine how many security related fixes there are between those two versions. How do we upgrade that? Is there something the general community can help with?
Thanks
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: