On a more serious note: speaking personally I welcome all donations of
old hardware that you're about to throw out. Well perhaps not all, I don't
have the space for an IBM mainframe or VAX.
-Nigel
--
Nigel Horne. Arranger, Composer, Typesetter.
NJH Music, Barnsley, UK. ICQ#20252325
[EMAIL
Nigel Horne wrote:
On a more serious note: speaking personally I welcome all donations of
old hardware that you're about to throw out. Well perhaps not all, I
don't have the space for an IBM mainframe or VAX.
Exactly what type of equipment? Bog standard pc hardware or the likes of
Sun,
On Friday 04 Mar 2005 13:57, Matt Fretwell wrote:
Nigel Horne wrote:
On a more serious note: speaking personally I welcome all donations of
old hardware that you're about to throw out. Well perhaps not all, I
don't have the space for an IBM mainframe or VAX.
Exactly what type of
We have some fairly busy mail servers that seem to run clamd fine for
days, and sometimes weeks, but since we moved to ClamAV 0.83 twice now
we've noticed that stream scanning, on rare occasions, starts to hold
connections and timeout.
Here is a clip from our log. clamd itself seems responsive
On Fri, 4 Mar 2005, Rob MacGregor wrote:
On Thu, 3 Mar 2005 22:26:18 +, Brian Morrison [EMAIL PROTECTED] wrote:
Announcement at
http://www.securityfocus.com/archive/1/392097/2005-02-28/2005-03-06/0.
The CVE referenced in it
Robert,
Do your mail logs show what came in just before the problems occurred (twice)?
It might just be that it falls into a class of email messages that cause
clamav ( 0.81 ) to go into hyperspace, examining each bit individually from
every point in five dimensions before giving the message
On Fri, 2005-03-04 at 09:05 -0500, Robert Blayzor wrote:
We have some fairly busy mail servers that seem to run clamd fine for
days, and sometimes weeks, but since we moved to ClamAV 0.83 twice now
we've noticed that stream scanning, on rare occasions, starts to hold
connections and timeout.
Trog wrote:
What software are you using to do stream scanning? It is switched off by
default in clamav-milter 0.83
I'm using a PERL script that is taking the messages and stream scanning
them with clamd. It's been running fine for many months with various
versions of clamd. I've just only
How has this issue been resolved? I have the exact same error trying
to compile and run clamav v0.83 from YDL 4.0 on a Mac mini. I can
compile and run v0.80 just fine, but it's out of date! v0.81 through
0.83 result in the clearerr error. Thanks.
Author: Morgan Smith
Date: 2005-02-04
Sam wrote:
That's odd. I've subscribed to Bugtraq for years, and they are usually
right on the spot with announcements liek this. .80 hasn't been current
for what, two months?
In this case I don't think it's BugTraq that's slow, I think it's
Conectiva. The CVE already lists advisories for
Just a general heads-up, until it's added to the virusdb. We've received
several of this in the past hour.
The payload is an .rar attachment with a random, numberic file name. The
.rar file always contains an executable .exe Otherwise the e-mail is
blank. From address is the To:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Steve Platt
Sent: vrijdag 4 maart 2005 16:40
To: ClamAV users ML
Subject: Re: [Clamav-users] ClamAV 0.83 - Stream scanning timeout
I paraphrase; but there was a problem in 0.82 and 0.83 which
Christopher X. Candreva wrote:
Just a general heads-up, until it's added to the virusdb. We've received
several of this in the past hour.
The payload is an .rar attachment with a random, numberic file name. The
.rar file always contains an executable .exe Otherwise the e-mail is
blank.
On Fri, 4 Mar 2005, Troy Ayers wrote:
bagle-rar variant probably... I submitted a sample, it was already detected...
you don't have scanrar commented out in your config do ya?
Yup -- but the last DB update (747) now catches it.
==
Chris
14 matches
Mail list logo
