Today, we are publishing a second release candidate for ClamAV 0.105.0.
Please help us validate this release by providing feedback via the ClamAV mailing list or on our Discord.
This
release candidate phase is expected to last for another four
weeks before the 0.105.0 Stable version is published. Please take this
opportunity to verify that 0.105.0 can build and run in your
environment.
Here's a rundown of what's changed since our first release candidate for 0.105.0:
- Fixed: Yara rules containing regex strings will load once more. This worked in previous ClamAV releases but was accidentally broken during 0.105 development.
- Fixed: In the Docker image, ClamD will now listen for IPv4 and IPv6 connections. Previousl,y it was hard-coded to listen on only 0.0.0.0 which made connections fail on some systems that prefer IPv6.
- Fixed: Assorted code quality issues.
- Added: A SigTool --fuzzy-img option to generate the image fuzzy hash. With this feature, analysts will not need to rely on ClamScan's debug output or the generated metadata JSON temp-file in order to generate hashes for new signatures.
Please submit bug reports to the ClamAV project GitHub Issues.
Refer to the initial 0.105.0 release candidate announcement blog post for the full list of improvements and changes in ClamAV 0.105.0.
