> On 18 Jan 2024, at 00:59, Michael Nolan <htf...@gmail.com> wrote: > On Wed, Jan 17, 2024 at 5:32 PM Daniel Gustafsson <dan...@yesql.se> wrote: >> >>> On 18 Jan 2024, at 00:24, Michael Nolan <htf...@gmail.com> wrote:
>>> I reinstalled the devel package, still get the same unresolved symbol error. >> >> My memory is failing me, but isn't CAST5 only available when loading the >> legacy >> provider in OpenSSL 3? Which providers are loaded in your openssl config? > > The legacy providers were enabled, disabling them worked. (The build > took a lot longer, too, but there were no obvious messages about > problems with the legacy providers enabled untilI ran the check.) That's surprising, I expected that it would require the legacy provider be loaded, not the other way around. OpenSSL works in mysterious ways though. -- Daniel Gustafsson
