[clamav-users] ClamAVR blog: ClamAV 0.99.4 has been released!

[Micah Snyder (micasnyd)]

All:

If this is in fact only occurring on Windows releases, I'm pretty sure this is my fault.

The way that the Windows ClamAV client receives the version string is slightly different than the POSIX versions.  In preparation for the 0.99.3 release, I discovered that our previous releases had broken version strings.

The TL;DR is that to fix the version string for windows, I hardcoded the version string on the Windows client for the first time and appear to have botched it slightly.  I apologize.  There isn't much to be done about it other than to ignore the warning.

The long story is:

For development builds, when compiling from a clone of the git repository, the Windows and POSIX builds pull a description of where the code came from using "git describe", which effectively is the most recent tag + the # of commits since that tag + a small hash.  This is done as a part of the ./configure (or ./win32/configure.bat) scripts.

For release builds, the version strings is supposed to get hardcoded.  This was being done correctly for non-Windows builds, but for Windows I found that the version string previous releases had not been correctly set.

As you demonstrated: on the 0.99.3 Windows release, if you run --version, you will get: ClamAV devel-clamav-0.99.2-30-g224f73461.  Freshclam identifies that it contains "devel" and thus does not warn you about the older version.

When I went to hardcode the version string for the 0.99.4 release I made an assumption about how the macro was used based on what the git tag would've provided and this resulted in the screwed up version string.

Again, sorry to cause this trouble.  I will see to it that the 0.100.0 release doesn't have the same issue.

Regards,
Micah


Micah Snyder
ClamAV Development
Talos
Cisco Systems, Inc.



On Mar 9, 2018, at 10:56 AM, Brian Fluet <decc at dec-clt.com<mailto:decc at dec-clt.com>> wrote:

On 9 Mar 2018 at 15:44, Kees Theunissen wrote, at least in part:

Clearly there is some imperfect comparison being performed prior to
issuing this message, when even identical "local" vs. "recommended"
versions are evaluated as "not equal".

The version strings "clamav-0.99.4" and "0.99.4" are not identical.
The package that you installed seems to have been built with a wrong
version string (including the phrase "clamav-").
How is your version shown by commands like "freshclam --version"
or "clamscan --version"?

~$ freshclam --version
ClamAV 0.99.4/24377/Fri Mar  9 10:13:20 2018
~$ clamscan --version
ClamAV 0.99.4/24377/Fri Mar  9 10:13:20 2018

In your case I would expect somthing like:
ClamAV clamav-0.99.4/24377/Fri Mar  9 10:13:20 2018

Running windows here with ClamD.  I retrieved the version info for clamscan, both 0.99.4 and
0.99.3.  You are correct in what 0.99.4 reports but notice what v0.99.3 reports.  There weren't
any version discrepancies warnings while running it though.  Hmmm.
Keep in mind that this is based on the following downloaded files:
clamav-0.99.4-win-x86.zip
clamav-0.99.3-windows-x86.zip files

Clamscan v0.99.4:
c:\clamav\clamscan --version
ClamAV clamav-0.99.4

Clamscan v0.99.3
c:\clamav_0_99_3\clamscan --version
ClamAV devel-clamav-0.99.2-20-g224f73461

Out of curiosity I retrieved the version info for clamd...

Clamd v0.99.4:
c:\clamav\clamd --version
ClamAV clamav-0.99.4/24377/Fri Mar 09 04:13:20 2018

Clamd v0.99.3:
c:\clamav_0_99_3\clamd --version
ClamAV devel-clamav-0.99.2-20-g224f73461/24377/Fri Mar 09 04:13:20 2018

--
Brian Fluet

_______________________________________________
clamav-users mailing list
clamav-users at lists.clamav.net<mailto:clamav-users at 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