[clamav-users] ClamAV(R) blog: ClamAV 0.102.0 Release Candidate is now available

G.W. Haywood clamav at jubileegroup.co.uk
Sat Oct 5 12:06:49 EDT 2019

Hi there,

On Sat, 5 Oct 2019, Dennis Peterson wrote:

> This particular hard requirement (libcurl) affects the communication channel 
> which is different than causing the code to fail to run at all. So the 
> question is do the new libcurl requirements immediately break existing 
> systems that are not yet updated with new libcurl functionality. ...

Sorry, I thought I'd explained in an earlier post.  I'm using libcurl v7.38.
So that I didn't need to update libcurl to v7.45 for clamonacc, I disabled it:

$ curl -V
curl 7.38.0 (x86_64-pc-linux-gnu) libcurl/7.38.0 OpenSSL[...snip,snip...]
$ head -7 ~/src/net/mail/clamav-devel-dev-0.102/config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by ClamAV configure 0.102.0-rc, which was
generated by GNU Autoconf 2.69.  Invocation command line was

   $ ./configure --disable-clamonacc
$ ps axufwww | grep freshclam | grep -v grep
clamav   14105  0.5  0.0 193092 13080 ?        Ss   Oct04   7:24 \
/usr/local/bin/freshclam -d --config-file=/etc/mail/clamav/freshclam.conf
$ freshclam -V --config-file /etc/mail/freshclam.conf
ClamAV 0.102.0-rc/25593/Sat Oct  5 09:30:21 2019
$ ls -l /var/lib/clamav/daily.cld
-rw-r--r-- 1 clamav clamav 147439104 Oct  5 10:44 /var/lib/clamav/daily.cld

> It is kind of a big deal to update a widely used library and creates
> knock-on problems from ripple effect for production systems subject
> to strong configuration management policies.

Not to mention publishing 0.102 with changes from 0.102rc which break it.



More information about the clamav-users mailing list