Topic: Updated ClamAV (0.95) - for impatient ones....

[Knuddi]

I know that the updated version of ClamAV (0.95) will come via the standard updates in SME, but for those of us who are impatient like children at Christmas it can still be installed/updated without problems:

Download the three packages from:

http://packages.sw.be/clamav/clamav-0.95-1.el4.rf.i386.rpm
http://packages.sw.be/clamav/clamav-db-0.95-1.el4.rf.i386.rpm
http://packages.sw.be/clamav/clamd-0.95-1.el4.rf.i386.rpm

Optional (I cannot recall why I have it - you might very well not need it):
http://packages.sw.be/clamav/clamav-devel-0.95-1.el4.rf.i386.rpm

And do a simple install afterwards
# rpm -Uvh clam*.rpm

Enjoy,
Jesper

Release Notes from ClamAV Team:

The following are the key features of this release:

    - Google Safe Browsing support: in addition to the heuristic and signature
      based phishing detection mechanisms already available in ClamAV, the
      scanner can now make use of the Google's blacklists of suspected
      phishing and malware sites. The ClamAV Project distributes a constantly
      updated Safe Browsing database, which can be automatically fetched by
      freshclam. For more information, please see freshclam.conf(5) and
      http://safebrowsing.clamav.net.

    - New clamav-milter: The program has been redesigned and rewritten from
      scratch. The most notable difference is that the internal mode has been
      dropped which means that now a working clamd companion is required.
      The milter now also has its own configuration file.

    - Clamd extensions: The protocol has been extended to lighten the load
      that clamd puts on the system, solve limitations of the old protocol,
      and reduce latency when signature updates are received. For more
      information about the new extensions please see the official
      documentation and the upgrade notes.

    - Improved API: The API used to program ClamAV's engine (libclamav) has
      been redesigned to use modern object-oriented techniques and solves
      various API/ABI compatibility issues between old and new releases.
      You can find more information in Section 6 of clamdoc.pdf and in
      the upgrade notes.

    - ClamdTOP: This is a new program that allows system administrators to
      monitor clamd. It provides information about the items in the clamd's
      queue, clamd's memory usage, and the version of the signature database,
      all in real-time and in nice curses-based interface.

    - Memory Pool Allocator: Libclamav now includes its own memory pool
      allocator based on memory mapping. This new solution replaces the
      traditional malloc/free system for the copy of the signatures that
      is kept in memory. As a result, clamd requires much less memory,
      particularly when signature updates are received and the database is
      loaded into memory.

    - Unified Option Parser: Prior to version 0.95 each program in ClamAV's
      suite of programs had its own set of runtime options. The new general
      parser brings consistency of use and validation to these options across
      the suite. Some command line switches of clamscan have been renamed
      (the old ones will still be accepted but will have no effect and will
      result in warnings), please see clamscan(1) and clamscan --help for
      the details.

[Knuddi]

Just noticed some warnings (WARNING: Ignoring deprecated option --disable-summary) in my log files after I installed There is a need to patch a file to get rid of these...

First make a backup of this file - (DO NOT SKIP THIS!)
/usr/share/qpsmtpd/plugins/virus/clamav

then open it with your preferred editor and go to line 190 that looks like this:

    . " --disable-summary $filename 2>&1";

Remove the "--disable-summary" so that the new lines looks like this:

    . " $filename 2>&1";

Save and exit and then restart mail system.

signal-event email-update

[CharlieBrady]

Just noticed some warnings (WARNING: Ignoring deprecated option --disable-summary) in my log files after I installed There is a need to patch a file to get rid of these...

Please post this information in the bug tracker.

[Knuddi]

Done - http://bugs.contribs.org/show_bug.cgi?id=5108

[cactus]

Relocating to SME 7.x Contribs as it is more appropriate there.

[mazkot]

reading what was updated have to wait since i have dansguardian installed...

[jpnelson40]

reading what was updated have to wait since i have dansguardian installed...

Could you elaborate? I did see dependency issues trying to install with the server-manager update, and also see "V3 DSA signature: BAD" when I try to 'rpm -Uvh' the clam*.rpm files. Maybe these are separate issues?

[cactus]

Could you elaborate? I did see dependency issues trying to install with the server-manager update, and also see "V3 DSA signature: BAD" when I try to 'rpm -Uvh' the clam*.rpm files. Maybe these are separate issues?

The signature is just noise, rpm (and hence yum) is not capable of only checking one signature AFAIK and there is also a version 4 one IIRC.

Second you should install using yum localinstall on SME Server 7 as this should automatically try to resolve dependencies which rpm won't do.

[jpnelson40]

Based on information that I found at: http://www.wains.be/index.php/2006/12/19/centosrhelfedora-web-proxy-antivirus-clamav/

I updated to the 0:0.95-1.el4.rf set this way:


#libclamav.so.5 needed for package: dansguardian
rpm -Uvh --force --nodeps clam*.rpm

ln -s /usr/lib/libclamav.so.6.0.2 /usr/lib/libclamav.so.5

followed by reconfiguration.

That worked for me.

[cactus]

Based on information that I found at: http://www.wains.be/index.php/2006/12/19/centosrhelfedora-web-proxy-antivirus-clamav/

I updated to the 0:0.95-1.el4.rf set this way:


#libclamav.so.5 needed for package: dansguardian
rpm -Uvh --force --nodeps clam*.rpm

ln -s /usr/lib/libclamav.so.6.0.2 /usr/lib/libclamav.so.5

followed by reconfiguration.

That worked for me.

Why did we even go this path... it seems to create more problems than solutions and will make it harder to revert to normal server behavior. I strongly suggest refraining from this procedure as the updates to clamav are usually pushed relatively quick and all the hassle is not worth the effort IMHO.