We plan to migrate away from MD5, and eventually stop supporting MD5 hash signatures as well.  I'm hopeful we can do it in the next feature version.  An internal MD5 implementation may be required if we can't fully migrate, but I suspect we should be able to.

Regards,
Micah


Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.
From: clamav-users <clamav-users-bounces@lists.clamav.net> on behalf of Andrew C Aitchison via clamav-users <clamav-users@lists.clamav.net>
Sent: Thursday, October 27, 2022 12:40 AM
To: Orion Poplawski via clamav-users <clamav-users@lists.clamav.net>
Cc: Andrew C Aitchison <clamav@aitchison.me.uk>
Subject: Re: [clamav-users] ClamAV on RHEL9 with FIPS enabled
 
On Wed, 26 Oct 2022, Orion Poplawski via clamav-users wrote:

> On 10/24/22 11:03, Hoevenaar, Jeffrey (GE Aerospace, US) via clamav-users
> wrote:
>> Hello,
>>
>> It would appear ClamAV will not run on RHEL9 with FIPS enabled.
>>
>> Has anyone else seen this issue?
>
> Known issue: https://github.com/Cisco-Talos/clamav/issues/564
>
> which it seems you have already found.

I guess that including an internal implementation of md5 would
enable ClamAV to run on FIPS enabled/compliant machines,
but that even so, this would not be the right thing to do ?

--
Andrew C. Aitchison                      Kendal, UK
                    andrew@aitchison.me.uk
_______________________________________________

Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation

https://docs.clamav.net/#mailing-lists-and-chat