[clamav-users] How the bad signature happened - conjecture (was Re: URGENT: Clamd is wedged on multiple installations)

Joel Esler (jesler) jesler at cisco.com
Fri Jan 26 17:29:27 UTC 2018

Steve Morgan, a developer here at Cisco that worked on ClamAV for about the past five years or so, decided to retire.  Monday was his last day.  On top of that, one our other developers (Micah) was out of the office today for a holiday, and so that only left, essentially myself and a couple other people to see this action on the list.

So while we regret the issue that this signature caused (and we will fix, not only the signature, but the code itself in an upcoming release), I am super proud of the community that came together and solved the problem.

Joel Esler | Talos: Manager | jesler at cisco.com<mailto:jesler at cisco.com>

On Jan 26, 2018, at 10:02 AM, Dianne Skoll <dfs at roaringpenguin.com<mailto:dfs at roaringpenguin.com>> wrote:

On Fri, 26 Jan 2018 06:44:30 -0800
"Jason J. W. Williams" <jasonjwwilliams at gmail.com<mailto:jasonjwwilliams at gmail.com>> wrote:

We started seeing this problem last night as well. Reading through the
thread, it doesn't appear that ClamAV has fixed the signatures yet
(as of 24257), or am I wrong?

Not only has it not been fixed, there hasn't been a peep out of the

This is NOT the way to deal with issues like this, especially in
security-sensitive software.


clamav-users mailing list
clamav-users at lists.clamav.net<mailto:clamav-users at lists.clamav.net>

Help us build a comprehensive ClamAV guide:


More information about the clamav-users mailing list