Roger that. On Fri, 21 Dec 2018 at 21:37, Joel Esler (jesler) <[email protected]> wrote:
> Yours is a separate issue that I have to look into. I have to pull the > logs and see why you are being blocked. > > Sent from my iPhone > > On Dec 21, 2018, at 14:22, Claudiu Albu <[email protected]> wrote: > > Micah, Al and all, > > > Thanks a lot again for your prompt reply and willingness to assist. > > I surely see the logic in your directions on how to get rid of the said > warning message, and I'll definitely store the provided details for when > the occasion arises. > > Nevertheless, my issue here was with not being able to perform hourly > updates via freshclam due to a 403 HTTP error, which I suspected was due to > our IP getting blocked - all that is described in the beginning of this > thread. > > Earlier on the version I installed from CentOS EPEL package - *.100.* > instead of *.101.* - was flagged as a related issue (?). I'll therefore > build the latest version from source and see how this goes. > > In case you can confirm the mentioned 403 error when updating has to do > with the hourly setting, I will put a local web server in place for it to > serve the signature updates. > > Happy holidays to everyone, too! > Thanks, > Claudiu > > On Fri, 21 Dec 2018 at 21:00, Micah Snyder (micasnyd) <[email protected]> > wrote: > >> Ignore my previous negativity. I spoke with the right folks and it is >> taken care of. It seems to be resolved in my own tests. >> >> Cheers, >> Micah >> >> Micah Snyder >> ClamAV Development >> Talos >> Cisco Systems, Inc. >> >> >> On Dec 21, 2018, at 1:46 PM, Micah Snyder (micasnyd) <[email protected]> >> wrote: >> >> Al's right, I think. We could set field 5 (or 4, 0-indexed) to '0' and >> that should actually disable the warning, as per these lines of code: >> >> https://github.com/Cisco-Talos/clamav-devel/blob/dev/0.101/freshclam/manager.c#L2588 >> >> I haven't had occasion to do it before, and it slipped by me when Al >> suggested it the first time. Sorry! Our operations group manages >> production server settings like this one so I would have to work with them >> to find the script and script options to set it. Regardless, it's a too >> late now. Most of our organization has off next week and the majority of >> people are already on vacation (myself-included, I just can't help checking >> my email). >> >> Happy Holidays everyone! >> -Micah >> >> Micah Snyder >> ClamAV Development >> Talos >> Cisco Systems, Inc. >> >> >> On Dec 21, 2018, at 1:17 PM, Al Varnell <[email protected]> wrote: >> >> So why not just turn the warning off by changing field #5 of the DNS >> response, as I suggested earlier? >> >> -Al- >> >> On Fri, Dec 21, 2018 at 08:56 AM, Micah Snyder (micasnyd) wrote: >> >> Just as a reminder, so no one is getting frustrated by the CentOS (or >> other distro) package maintainers: >> We (ClamAV team) made a mistake in the ClamAV 0.101.0 header files >> impacting projects downstream that rely on our library. I just re-posted >> the details from our previous disclosure in a new blog entry, to reach a >> wider audience since a lot of folks probably didn't see the mailing list >> annoucement: >> https://blog.clamav.net/2018/12/libclamav-missing-headers-issue.html >> >> Because of the header file issue, package maintainers have been holding >> off until we get a patch release out. >> >> Sorry for the inconvenience! >> Micah >> >> Micah Snyder >> ClamAV Development >> Talos >> Cisco Systems, Inc. >> >> >> On Dec 21, 2018, at 9:12 AM, Benny Pedersen <[email protected]> wrote: >> >> Claudiu Albu skrev den 2018-12-21 13:56: >> >> CLAMAV VERSION is: >> "_WARNING: Local version: 0.100.2 Recommended version: 0.101.0_" >> After some reading, this seems to be the latest version in a stable >> CentOS EPEL stable repo - correct? >> >> >> no >> >> freshclam reports latest stable version, its upto centos maintainrs to >> put that version into there repo, 2 options now is, wait, build rpms localy >> self, and install that rpm update >> >> http://lifeofageekadmin.com/build-rpms-centos/ >> >> why wait ? :=) >> _______________________________________________ >> clamav-users mailing list >> [email protected] >> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users >> >> >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml >> >> >> _______________________________________________ >> clamav-users mailing list >> [email protected] >> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users >> >> >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml >> >> >> -Al- >> -- >> Al Varnell >> Mountain View, CA >> >> >> >> >> _______________________________________________ >> clamav-users mailing list >> [email protected] >> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users >> >> >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml >> >> >> _______________________________________________ >> clamav-users mailing list >> [email protected] >> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users >> >> >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml >> >> >> _______________________________________________ >> clamav-users mailing list >> [email protected] >> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users >> >> >> Help us build a comprehensive ClamAV guide: >> https://github.com/vrtadmin/clamav-faq >> >> http://www.clamav.net/contact.html#ml >> > _______________________________________________ > clamav-users mailing list > [email protected] > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml > > _______________________________________________ > clamav-users mailing list > [email protected] > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml >
_______________________________________________ clamav-users mailing list [email protected] http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
