Re: [clamav-users] ClamAV® blog: The ClamAV 0.101.0 release candidate is here!

Hi Dennis, Nope. We haven't made any changes to the clamd socket API. -Micah Micah Snyder ClamAV Development Talos Cisco Systems, Inc. On Nov 22, 2018, at 6:11 PM, Dennis Peterson mailto:denni...@inetnw.com>> wrote: Does this change how socket-connected clients (milters, for example) comm

Re: [clamav-users] ClamAV® blog: The ClamAV 0.101.0 release candidate is here!

Does this change how socket-connected clients (milters, for example) communicate? On 11/19/18 11:40 AM, Joel Esler (jesler) wrote: # Changes to the libclamav API: * Those who build applications around our shared library will need to change how they declare and pass scanning options to li

Re: [clamav-users] ClamAV® blog: The ClamAV 0.101.0 release candidate is here!

Paul Kosinski skrev den 2018-11-20 02:54: Are there any other users of HAVP in conjunction with ClamAV? (HAVP was originally written to work with ClamAV as well as other AV packages, such as Kaspersky, Sophos and F-Prot.) recompile of havp should be solve it, unless havp have bugs to solve le

Re: [clamav-users] ClamAV® blog: The ClamAV 0.101.0 release candidate is here!

I have long been using HAVP with ClamAV to scan HTTP traffic (inbound). HAVP uses libclamav directly (rather than e.g., clamd) so it doesn't have an excessive performance impact. (Cf. http://www.havp.org/) Unfortunately, HAVP hasn't seen any development for a bit over 2 years. In the past, simply

[clamav-users] ClamAV® blog: The ClamAV 0.101.0 release candidate is here!

https://blog.clamav.net/2018/11/the-clamav-01010-release-candidate-is.html The ClamAV 0.101.0 release candidate is here! The ClamAV 0.101.0 release candidate is here! We have also made significant improvements to our User Manual