Re: [clamav-users] ClamAV 0.105 release candidate

## Joel Esler via clamav-users (clamav-users@lists.clamav.net): > Can’t use wget. Looks like "can't use anything which doesn't look like a web browser", as BSD fetch hits the 403, too. That's a major PITA on the BSD side (just like openSuse), but it was working just fine at the time of the 0.10

Re: [clamav-users] Anyone notice any issues with clamav 0.99.2 and recent patterns?

## Karl Pielorz (kpielorz_...@tdx.co.uk): > We're currently running clamav 0.99.2 (technically shown as 0.99.2_8) under > FreeBSD 10.3 amd64 - since then we've seen an issue where clamd "kind of > dies" - it's still running, there are no errors logged anywhere (we log to > syslog) - but whilst

Re: [clamav-users] ClamAV®: ClamAV 0.98 has been released!

## Al Varnell (alvarn...@mac.com): > > ClamAV 0.98 has been released! > > As usual, it was not linked to the main ClamAV® web page yet, but I was able > to track it down here: > . Well, it's not even listed on the DNS: ClamAV update pro

[clamav-users] recurrent FP Win.Trojan.Swrort-2293

Hi, I just re-reported a FP on signature Win.Trojan.Swrort-2293. The md5sum of the file in question is 26f868a9dd7b213f53d415311a70973c. I already reported this exact file (which is a sample from our "clean collection") as a FP on 2013-01-16 (first daily cvd to trigger the signature was 16495) and

Re: [clamav-users] Value too large for defined data type

## Török Edwin (ed...@clamav.net): > I think I got it: > off_t st_size;/* total size, in bytes */ > > The st_size member of the stat buffer is a signed value, so any file over 2GB > in size > would be negative. stat() won't allow that so instead it returns an error > telling

Re: [clamav-users] daily database broken again

Hi, just an idea for those insisting on running old versions: After some simple tests I believe it's possible to get your own "database check" even on versions older than 0.96.x (4?). Have freshclam update the signatures into a testing directory, not the "real" clamav database dir (that's what Dat

Re: [Clamav-users] clamd stuck at 100% cpu usage

## Roberto Ullfig ([EMAIL PROTECTED]): > We've also seen clamd stuck at 100% when PDF scanning (new feature > introduced recently) large files. We've disabled PDF scanning for now. > We will need to put in our own check to prevent PDF scanning of files > over a certain size. I've seen a simila

Re: [Clamav-users] bug in clamdscan

## Steven Stern ([EMAIL PROTECTED]): > The same thing happens in 0.73. Reading the man page, it seems that it is a > WAD. > clamdscan [options] [file/directory] > clamdscan scans one file or one directory tree > clamscan works on multiple files. Have a look at the source :) - clamav-0.73/clamsca