this will be fixed? Between the fp's for --detect-
structured=yes and these fp's for trojans Clamscan is becoming, IMHO,
its own worst enemy.
Frank Sfalanga Jr. | Director of Information Technology
Ph. 239-221-3309 | fr...@csiglobalvcard.com<mailto:fr...@csiglobalvcard.com>
CSI Enterprise
Hello,
I'm getting conflicting reports of SSN found within log files. If I use
the '--detect-structured=yes' switch I get this result
root@CSI-app1:/var/log# clamscan -v -i -r --detect-structured=yes
auth.log.3
Scanning auth.log.3
auth.log.3: Heuristics.Structured.SSN FOUND
--- SCAN
Bob Hutchinson wrote:
On Friday 29 Jul 2005 21:29, Dawson wrote:
My problem is probably very simple for all the
experts out there but has stumped me
my freshclam.og is in /var/log
I set the ownership to clamav
It gets reset to root and then prevents the
program from running. You can
I recently built a new qmail server using the process at qmailrocks.org
from which I compiled/installed ClamAV 0.83. Later I upgraded to ClamAV
0.86.2 using this procedure:
* Download latest tarball from http://clamav.net and place it in the
/downloads/qmailrocks/ directory
* Untar and
Daniel wrote:
It looks like you have installed different versions of clamav in /usr
and /usr/local
Try
which -a freshclam
which -a clamscan
I did have two versions. The original RPM installed to /usr/bin with
the config files in /etc. The compiled version installed the binaries
in
