Comment 1 Ingo Steuwer 2013-12-10 17:00:46 CET

occures with UCS 2.4, UCS 3.1 and UCS 3.2

Comment 2 Stefan Gohmann 2013-12-10 19:12:11 CET

A backport for UCS 3.1 and 2.4 should also be checked.

Comment 3 Moritz Muehlenhoff 2013-12-11 10:16:32 CET

This is a misleading status message by ClamAV; the check is only based on a comparison of version strings. While the FAQ may indicate differently, the current versions in UCS 2.4 to 3.1 can actually process all current malware signatures:

From the output of freshclam:

main.cvd is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)
daily.cld is up to date (version: 18223, sigs: 596031, f-level: 63, builder: neo)
bytecode.cvd is up to date (version: 233, sigs: 44, f-level: 63, builder: dgoddard)

The required engine features for clamav are denoted in "functionality levels", i.e. the most recent level required by the standard CVD files is 63.

Unfortunately the current functionality level of the installed cannot easily be detected with any of the tools shipped by ClamAV, but only through the API:

#include <stdio.h>
#include "clamav.h"

int main(void)
{
        printf("%d", cl_retflevel());
}

The clamav version in UCS 2.4/3.1 provides functionality level 68 and the version in UCS 3.2 functionality level 69.

Nonetheless, the status message will be removed since it's a source of confusion (previously also reported as Bug 25808)

In addition Bug 33716 was created to integrate ClamAV tests for non-processable signatures into the daily ucs-test runs.

Comment 4 Moritz Muehlenhoff 2013-12-11 10:33:49 CET

(In reply to Moritz Muehlenhoff from comment #3)
> This is a misleading status message by ClamAV; the check is only based on a
> comparison of version strings. While the FAQ may indicate differently, the
> current versions in UCS 2.4 to 3.1 can actually process all current malware
> signatures:

I meant 2.4 to 3.2

Comment 5 Moritz Muehlenhoff 2013-12-11 10:35:44 CET

*** Bug 25808 has been marked as a duplicate of this bug. ***

Comment 6 Moritz Muehlenhoff 2013-12-12 12:17:37 CET

The misleading error is now removed.

YAML: 2013-12-12-clamav.yaml

Comment 7 Erik Damrose 2014-01-09 12:57:57 CET

OK: Warning message from comment 0 removed.

FAIL: The duplicate bug mentions a different warning message. It is printed in libclamav/cvd.c:

LibClamAV Warning: ***********************************************************
LibClamAV Warning: ***  This version of the ClamAV engine is outdated.     ***
LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq ***
LibClamAV Warning: ***********************************************************

It should also be removed.

Comment 8 Moritz Muehlenhoff 2014-01-14 13:23:13 CET

(In reply to Erik Damrose from comment #7)
> OK: Warning message from comment 0 removed.
> 
> FAIL: The duplicate bug mentions a different warning message. It is printed
> in libclamav/cvd.c:
> 
> LibClamAV Warning:
> ***********************************************************
> LibClamAV Warning: ***  This version of the ClamAV engine is outdated.    
> ***
> LibClamAV Warning: *** DON'T PANIC! Read http://www.clamav.net/support/faq
> ***
> LibClamAV Warning:
> ***********************************************************
> 
> It should also be removed.

The additional log message has been removed as well.

Comment 9 Erik Damrose 2014-01-14 14:03:19 CET

OK: Patch removes the second warning message
OK: YAML file
-> Verified

Comment 10 Moritz Muehlenhoff 2014-01-21 14:08:36 CET

http://errata.univention.de/ucs/3.2/24.html