In the forum a user has reported a problem with dnsdist reporting that it can not find libsodium.so.23 https://community.ipfire.org/t/strange-error-in-2-27/8584 libsodium was committed as a new core package but it looks like it was not shipped with CU170. I have confirmed on my CU170 that libsodium.so.23 is not present. Libsodium is also not listed in the Core Update filelists file. I also confirmed that installing dnsdist gives the error message about libsodium.so.23 not being found.
https://patchwork.ipfire.org/project/ipfire/patch/22a3abec-9261-38e5-3108-2269752258f4@ipfire.org/
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=76d9ce6b11f01600c88641f022dc64a260fdf9b1
Is there any way we can release this fix sooner than with 171?
Hi Michael, See my dev mailing list email. https://lists.ipfire.org/pipermail/development/2022-September/014418.html Depends if you want to ship libsodium as a core package or if it should not be shipped and dnsdist should have the use of libsodium disabled?
Decision to stay with the shipping of libsodium. https://lists.ipfire.org/pipermail/development/2022-September/014460.html Tested out CU171 unstable on a vm testbed and confirmed that dnsdist no longer has a problem with missing libsodium.
https://blog.ipfire.org/post/ipfire-2-27-core-update-171-is-available-for-testing
Tested out on CU171 Testing on my vm testbed. Using a dnsdist.conf file from the addon's website I was able to successfully get dnsdist to start.
https://blog.ipfire.org/post/ipfire-2-27-core-update-171-released-security-advisory