Any hope for eliminating the delay during the reload of the signatures? It blocks the milter and SMTP server for a while.

Thanks a lot

 Marco

Il 06/02/2018 00:03, Joel Esler (jesler) ha scritto:


http://blog.clamav.net/2018/02/clamav-01000-beta-has-been-released.html

ClamAV 0.100.0 beta has been released!
ClamAV 0.100.0-beta is the successor to the previous 0.99.3-beta2.  The 0.99.3 patch 
release on January 25th was required to address vulnerability fixes in a timely 
manner, so the features previously found in 0.99.3 betas have been bumped to this new 
version.  If you haven’t read it, please read the announcement regarding the version 
number change. 
<http://blog.clamav.net/2018/01/clamav-version-number-adjustment.html>

The 0.100.0-beta includes all of the feature improvements and bug fixes that 
were in the previous 0.99.3-beta2, plus some additional bug fixes and requested 
improvements that were found by users of the previous beta.  These include:


   *   Eliminating warnings regarding with variables being used before being 
initialized.
   *   Correcting an issue for those using private mirrors where freshclam 
attempts to pull down the CVD file if the CLD is up-to-date.
   *   Fixed a bug in the filtering system that caused unexpected behavior for 
signatures that use the case insensitive signatures (:i).
   *   Increased the max stack size when building ClamAV for non-glibc Linux 
machines (i.e. musl).
   *   Deprecated the AllowSupplementaryGroups config option in a more graceful 
way.
   *   Bug fixes to on-access scanning.
   *   A few other bug fixes.


We could use community support testing these fixes, of course.  That said, our 
main goal of 0.100.0-beta is to get the community ready for the version string 
change.  Mirror maintainers have been asked to verify that ClamAV clients using 
the 0.100.0 version number in the HTTP user agent are not blacklisted by 
regexes intended to drop support for older versions of ClamAV.

As a disclaimer, 0.100.0-beta isn’t a release candidate because we have a few 
outstanding known issues that we must address prior to the 0.100.0 release, and 
because once the fixes are made we will have to complete regression testing.  
The known issues blocking release include the following:


   *   The libmspack library install location, name. 
Bug<https://bugzilla.clamav.net/show_bug.cgi?id=11994>
   *   BlockMax config option may differ slightly from —block-max command line 
option. Bug<https://bugzilla.clamav.net/show_bug.cgi?id=11970>
   *   Using the ./configure --disable-static will still require llvm-static. 
Bug<https://bugzilla.clamav.net/show_bug.cgi?id=11995>
   *   Improvements in PDF object parsing (in progress).
   *   Messages when clamscan skips a file due to max file size settings, along with 
corrections to the —help string. 
Bug<https://bugzilla.clamav.net/show_bug.cgi?id=11967>
   *   Warnings when building on macOS.  
Bugs<https://bugzilla.clamav.net/show_bug.cgi?id=11747>, 
Bugs<https://bugzilla.clamav.net/show_bug.cgi?id=11977>

Bugs should be brought to our attention via the clamav-devel mailing 
list<https://www.clamav.net/contact#ml> or via 
bugzilla<https://bugzilla.clamav.net/>


--
Joel Esler | Talos: Manager | jes...@cisco.com<mailto:jes...@cisco.com>






_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml


_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users


Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml

Reply via email to