it
into ClamAV's signature database directory and you should be good
to go.
Cheers,
Matthew
--
Matthew Newton, Ph.D. m...@le.ac.uk
Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
For IT help contact helpdesk extn. 2253
generally apply security patches. There was a volatile
repository once as they realised that software like ClamAV needs
updating more but conflicted with normal policy; it looks like
it's been replaced, but I don't know if they still maintain the
ClamAV package there.
Cheers,
Matthew
--
Matthew
as malware in any other scanners (checked
with a couple of on-line multi-scanner sites - only ClamAV hits.
Cheers,
Matthew
--
Matthew Newton, Ph.D. [EMAIL PROTECTED]
Systems Architect (UNIX and Networks), Network Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
as
CL_TYPE_BINARY_DATA). Also, we now have a bug entry for this problem:
That's great, thanks - all test files I have now scan OK.
Does the above alter much else in the scanning?
Many thanks,
Matthew
--
Matthew Newton, Ph.D. [EMAIL PROTECTED]
Systems Architect (UNIX and Networks), Network Services,
I.T
On Fri, Oct 17, 2008 at 05:23:06PM +0200, Tomasz Kojm wrote:
On Fri, 17 Oct 2008 15:53:08 +0100
Matthew Newton [EMAIL PROTECTED] wrote:
That's great, thanks - all test files I have now scan OK.
Does the above alter much else in the scanning?
No, it doesn't.
Excellent, thanks
