It was an included dependency that due to build configuration was using libcrypto but rather including its own MD5_Final, which then the loader selected when another shared object (libclamav) was loaded.
On Tue, Feb 10, 2026 at 11:53 AM Sebastian Andrzej Siewior < [email protected]> wrote: > On 2026-02-10 09:12:11 [-0800], Max Burke wrote: > > Turns out this is not an openssl issue but an issue with another shared > > library that provides conflicting MD5 functions. Apologies for wasting > your > > time. > > Which library and how was linked? Or was it pre-loaded? > > > -Max > > Sebastian > -- -Max
