Bug 12929

Summary: Core Update 170 - libsodium required by dnsdist but not shipped
Product: IPFire Reporter: Adolf Belka <adolf.belka>
Component: ---Assignee: Peter Müller <peter.mueller>
Status: CLOSED FIXED QA Contact:
Severity: Crash    
Priority: Will only affect a few users CC: michael.tremer, peter.mueller
Version: 2Keywords: 5MinuteJob
Hardware: unspecified   
OS: Unspecified   

Description Adolf Belka 2022-09-17 08:34:14 UTC 
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.
Comment 3 Michael Tremer 2022-09-18 09:25:07 UTC 
Is there any way we can release this fix sooner than with 171?
Comment 4 Adolf Belka 2022-09-18 10:49:47 UTC 
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?
Comment 5 Adolf Belka 2022-10-03 08:36:59 UTC 
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.
Comment 7 Adolf Belka 2022-10-06 12:32:55 UTC 
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.