[clamav-users] update report

Micah Snyder micasnyd at sourcefire.com
Thu Jul 5 15:39:56 EDT 2018


Sorry for the delayed response, all:

The issue facing those without IPv6 compatible hardware or networks came to light earlier in the CloudFlare mirror-transition.  A ticket that both alerted us to the issue and provided a fix was prvoided in a bug courtesy of Guilherme Benkenstein:
https://bugzilla.clamav.net/show_bug.cgi?id=12119

As stated in the final comment, I have added the patch to our development branch for v0.101 and the upcoming v0.100.1 patch release.

0.101:
https://github.com/Cisco-Talos/clamav-devel/commit/f4861c670167a7a109340c1f8579a55205acbd8a

0.100.1:
https://github.com/Cisco-Talos/clamav-devel/commit/9fd6d90afab40b5e3e3fe456d337eecce670fa50

The 0.100.1 patch release is in testing and will be published very soon.  My apologies to those who have been frustrated by IPv4-IPv6 related connection issues.  With any luck, this patch release will resolve things.

Regards,
Micah


On Jul 2, 2018, at 1:56 PM, Joel Esler <jesler at cisco.com<mailto:jesler at cisco.com>> wrote:
> On Jul 2, 2018, at 1:56 PM, Gene Heskett <gheskett at shentel.net<mailto:gheskett at shentel.net>> wrote:
> 
> but even on my setups which have this for years freshclam repetaly
> produces ipv6 crap-messages which is simpyl wrong
> 
> If thats the case, and I'll find out by this time tomorrow, then I can't
> help but agree, its a bug. Not a showstopper, but one to be swatted in
> the next upgrade for us folks out here in the ipv4 only puckerbrush.
> 
> 
> It's definitely on our radar.  Micah may want to comment further.
> 
> --
> Joel Esler
> Sr. Manager
> Open Source, Design, Web, and Education
> Talos Group
> http://www.talosintelligence.com


More information about the clamav-users mailing list