> Please run clamscan in debug mode over these files (--debug).
I have appended the output for file2 and file3 to this email.
In both cases, the increased memory consumption starts when the following lines
are printed:
LibClamAV debug: Calculated MD5 checksum: a07774f93dc2c5da62ddf502692a208e
Li
Hi!
As announced, I have done some testing with files containing garbage.
I start a new thread as I want to get away from the vmware image related
discussion.
On my X86_64 SuSE 10.1 system, equipped with 4GB main memory, I have installed
the "standard" rpm
clamav-0.88.7-1.2.x84_64.rpm that can
> My experience: vmdk-file can't be properly scanned without accounting for
> the vmdk base of the file. They are not files Clamav understands. Just as
> zip files need special handling, vmdk files need special handling. VMware
> has published the specs. I don't have the time/smarts to process
> I don't know the format of a VMWare file. Is it useful to scan it (or are
> the contents enough unlike what a scanner knows about that problems are
> unlikely to be seen anyhow)? Perhaps it makes more sense to scan VMs from
> within the VM.
I do not want to scan it, but I tried out clamav, and
On my X86_64 SuSE 10.1 system, equipped with 4GB main memory, I have installed
the "standard" rpm
clamav-0.88.7-1.2.x84_64.rpm that can be downloaded from ftp.suse.com. When I
scan a 3.5GB file
(in fact it is a VMWARE vmdk-file and not an archive) with clamd/clamdscan, all
seems to run ok
unt
