clamav-users June 2008 archive
Main Archive Page > Month Archives  > clamav-users archives
clamav-users: [Clamav-users] [Fwd: [Clamav-devel] 0.93.1 / libcl

[Clamav-users] [Fwd: [Clamav-devel] 0.93.1 / libclamav: no CL_EMAX*-Error-Codes for Applications?]

From: Marcus Neukert <marcus.neukert_at_nospam>
Date: Fri Jun 13 2008 - 13:09:14 GMT

Forwarding to clamav-users-list, hoping for an answer ...

  • Original-Nachricht -------- Betreff: [Clamav-devel] 0.93.1 / libclamav: no CL_EMAX*-Error-Codes for Applications? Datum: Wed, 11 Jun 2008 12:30:35 +0200 Von: Marcus Neukert <> Antwort an: ClamAV Development <> An: ClamAV Development <> Referenzen: <> <>


following has changed in clamav-0.93.1 (see Changelog):

Mon Apr 28 16:13:33 CEST 2008 (tk)
  • libclamav/scanners.c: don't return CL_EMAX* error codes to applications (bb#1001)

If a limit wae reached, the return-code for applications is: CL_CLEAN. (see scanners.c / cli_magic_scandesc):

switch(ret) { case CL_EFORMAT: case CL_EMAXREC: case CL_EMAXSIZE: case CL_EMAXFILES: cli_dbgmsg("Descriptor[%d]: %s\n", desc, cl_strerror(ret)); return CL_CLEAN; default: return ret;

Now, when scanning an archive which does contain more files than configured in cl_limits.maxfiles, the scan will end when the limit is reached and the Result of the scanner is CL_CLEAN !!, although the following files after reaching the limit have not been scanned and can possibly be infected.

What is the reason for changing this behaviour? IMHO the scanner should return the CL_EMAX* error-code to inform the application that the scanned file can possibly be infected.

Marcus Neukert -- Marcus Neukert Softwareentwickler - New Technology Tel. +49-721-91374-3943 · Fax +49-721-91374-2740 · 1&1 Internet AG Brauerstraße 48 76135 Karlsruhe Amtsgericht Montabaur HRB 6484 Vorstand: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Matthias Greve, Robert Hoffmann, Markus Huhn, Oliver Mauss, Achim Weiss Aufsichtsratsvorsitzender: Michael Scheeren _______________________________________________ Help us build a comprehensive ClamAV guide: visit