What am I missing?
I believe Kevin is seeking an option similar to clamd's LogClean option
in clamav-milter.
From clamd.conf:
# Also log clean files. Useful in debugging but drastically increases
the
# log size.
# Default: no
LogClean yes
Craig is correct - I would like
Suntower West wrote:
Hi,
I'm getting a positive for this in a Eudora mailbox (which is
basically just an ASCII file.) However, when I scan the same file
with Comodo it comes up as clean.
Today clamav found the same in
clamav-users Digest, Vol 55, Issue 15 ...
Wolfgang
This has been submitted as bug 1567:
https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1567
--
Jay Deiman
\033:wq!
___
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
Wolfgang Cernohorsky wrote:
Suntower West wrote:
Hi,
I'm getting a positive for this in a Eudora mailbox (which is
basically just an ASCII file.) However, when I scan the same file
with Comodo it comes up as clean.
Today clamav found the same in
clamav-users Digest, Vol 55, Issue 15
Kevin Clark wrote:
Craig is correct - I would like clamav-milter to log clean files as well as
infected ones much like it used to.
Hi Kevin,
I think this is pretty pointless as that would basically duplicate any
line already in the logs. That's expecially true if you are logging via
syslog.
Kevin Clark wrote:
What am I missing?
I believe Kevin is seeking an option similar to clamd's LogClean option
in clamav-milter.
From clamd.conf:
# Also log clean files. Useful in debugging but drastically increases
the
# log size.
# Default: no
LogClean yes
Craig is
Currently, I am tracking 233 files containing malware that have been
submitted both directly to clamav.net and virustotal.com and yet
continue not to show up in the signature database so that they can be
detected. My scripts check them frequently against the current clamav
databases using
Hello,
I have been running clamav version = 0.94 years on my Power Mac G5 with
yellowdog linux 4.1. Starting from clamav 0.94.1, I am beginning to have
problem with:
./freshclam/freshclam -V
/usr/src/clamav-0.94.1/freshclam/.libs/lt-freshclam: error while loading
shared libraries:
Vincent
Can't comment on Yellow Dog but using gcc 4.2, clamav 0.95.1 works
fine under OSX 10.4 and 10.5. I had problems with gcc 3.4.
Hope this helps
Tom
At 3:31 PM -0700 4/17/09, Vincent Li wrote:
Hello,
I have been running clamav version = 0.94 years on my Power Mac G5 with
yellowdog linux
On Fri, 17 Apr 2009, Vincent Li wrote:
Hello,
I have been running clamav version = 0.94 years on my Power Mac G5 with
yellowdog linux 4.1. Starting from clamav 0.94.1, I am beginning to have
problem with:
./freshclam/freshclam -V
/usr/src/clamav-0.94.1/freshclam/.libs/lt-freshclam: error
On Fri, Apr 17, 2009 at 05:34:58PM -0700, Vincent Li said:
On Fri, 17 Apr 2009, Vincent Li wrote:
# ldd /usr/local/bin/freshclam
libclamav.so.5 = /usr/local/lib/libclamav.so.5 (0x0fee9000)
# /usr/local/bin/freshclam -V
/usr/local/bin/freshclam: error while loading shared
Tom Shaw wrote:
Currently, I am tracking 233 files containing malware that have been
submitted both directly to clamav.net and virustotal.com and yet
continue not to show up in the signature database so that they can be
detected. My scripts check them frequently against the current clamav
Tom Shaw wrote:
What I would like (and I think that others that submit malware files
to clamav.net would like) is for clamav.net to provide a method for
us to programmatically query to determine if either 1) the file has
already been determined by clamav to be not malicious or 2) you have
13 matches
Mail list logo
