Hi there,
On Fri, 6 Nov 2009 Nathan Gibbs wrote:
Cut these guys some slack.
They can't do everything.
This isn't about cutting slack, or for that matter pointing fingers.
It's about contributing. I'm contributing. Sometimes people don't
want to hear what needs to be said. That can be
* G.W. Haywood wrote:
Hi there,
On Fri, 6 Nov 2009 Nathan Gibbs wrote:
Cut these guys some slack. They can't do everything.
This isn't about cutting slack, or for that matter pointing fingers.
It's about contributing. I'm contributing. Sometimes people don't
want to hear what needs
* aCaB wrote:
G.W. Haywood wrote:
I suspect that rather than QA, what you do is just a lot of hap-hazard
testing. That's why, whenever I see a new release of ClamAV, first I
will suppress a groan and then, before I risk it on any of my servers,
I'll wait a while and watch the users' list to
Hello again,
On Wed, 4 Nov 2009 aCaB wrote:
G.W. Haywood wrote:
I suspect that rather than QA, what you do is just a lot of hap-hazard
testing.
My mail was about custom databases provided by 3rd parties, not about
ClamAV release cycles.
Besides, you miss another point: ClamAV is an
G.W. Haywood wrote:
I suspect that rather than QA, what you do is just a lot of hap-hazard
testing. That's why, whenever I see a new release of ClamAV, first I
will suppress a groan and then, before I risk it on any of my servers,
I'll wait a while and watch the users' list to see how much
Hi there,
On Thu, 29 Oct 2009 aCaB wrote:
On our side we do a lot of QA
...
I really believe something needs to happen here so that these type of
bugs can be caught quickly before they affect a number of users.
Thoughts?
I suspect that rather than QA, what you do is just a lot of
Steve Basford wrote:
LibClamAV Error: mpool_malloc(): Attempt to allocate 2097152 bytes.
Please report to http://bugs.clamav.net
LibClamAV Error: cli_ac_addpatt: Can't realloc ac_pattable
LibClamAV Error: cli_parse_add():
Thanks to the ClamAV team, the bug was fixed in the clamav-devel
On Sun, Oct 25, 2009 at 11:27 AM, Steve Basford
steveb_cla...@sanesecurity.com wrote:
Hi All,
Some users (mainly x86_64 so far) noticed database errors (malformed
database) when loading signatures.
As signature integrity is checked before upload to the mirrors and the
download scripts
Hi All,
Some users (mainly x86_64 so far) noticed database errors (malformed
database) when loading signatures.
As signature integrity is checked before upload to the mirrors and the
download scripts check integrity before use, this issue should not arise.
With help from various people on
