Clamwin 0.97.5, W XP Prof.

When I scan a .ogv file, clamwin doesn't do a scan. (It does on other types of files.) "Data scanned: 0.00 MB" Preferences/Filters is not set to not scan .ogv files.

----------- SCAN SUMMARY -----------
Known viruses: 1300780
Engine version: 0.97.5
Scanned directories: 0
Scanned files: 1
Infected files: 0

Data scanned: 0.00 MB
Data read: 171.36 MB (ratio 0.00:1)
Time: 220.978 sec (3 m 40 s)
[usually takes about thirty seconds on this old computer, this time my browser was doing an automated online update at the same time...]

--------------------------------------
Completed
--------------------------------------

The file I used was:
https://archive.org/details/TheHuntForGollum
https://archive.org/download/TheHuntForGollum/d23omsfsowlps.ogv
(btw quite a nice fan created movie.)

Did I miss something, or is something wrong with Clamwin?

thanks/Rolf

The OGV file extension is a video file. Many videos are quite large. By default, ClamWin does not scan a file larger than 100 megabytes, so your file is probably not being scanned by ClamWin because it is larger than 100 MB. If that is the case with your ogv file, you need to increase the ClamWin defajult scan limit. If this is not the reason it is not scanned, and you are using a custom set of extensions to scan, then include .ogv in the extensions.


I think the 100 MB size limit is very generous, and it will let ClamWin scan 99.9999% of files that would contian a virus. Most viruses are under 1 MB in size, and the majority of virus files are under 500 KB. Most trojan downloaders are under 100 KB in size. Today's viruses are generally designed to make money for someone as long as possible, and they try to be stealthy. A 100 MB or larger file is not stealthy! It also take a bit of programming knowledge to plant a virus in a video file.

I would leave the CalmWin scan limit at the 100 MB default and not worry about it.

Regards,

I already did that, both for "all files" and "archives". Still no go.

cheers/Rolf

Hmmm. Well, I understand that the next version of Clam AV will correct the error notice received sometimes during scanning of some files, and ClamWin will get the fix when they do their Windows port of Clam AV--don't know when this will be though--could be next year. You don't seem to have such a notice during your scans, but maybe it will fix things.

It could also very well be that the Clam scanning engine just can't handle this file type--I haven't seen it myself. At the moment, I wouldn't worry too much about not being able to scan it. I don't think you have much worry about malware infecting it.

Regards,