Roger that.
On Fri, 21 Dec 2018 at 21:37, Joel Esler (jesler) 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 wrote:
>
> Micah, Al and all,
>
>
> Than
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 wrote:
>
> Micah, Al and all,
>
>
> Thanks a lot again for your prompt reply and willingness to assist.
>
> I su
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
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)
mailto:micas...@cisco.com>> wrote:
Al's
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 s
Al,
Sorry, looked again but haven't received such suggestion so far.
Can you please tell me a bit more about what you mean?
Thanks a lot.
On Fri, 21 Dec 2018 at 20:17, Al Varnell wrote:
> So why not just turn the warning off by changing field #5 of the DNS
> response, as I suggested earlier?
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
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
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 maint
Thanks for the prompt reply,
*IP is*: 193.181.246.98
*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?
Regards,
*Claudiu ALBU*
On Fri, 21 Dec 2018 at 14:37
Please see other other email.
Sent from my iPhone
> On Dec 21, 2018, at 06:11, Claudiu Albu wrote:
>
> Hello all,
>
>
> Been browsing through similar previous occurrences but found nothing
> conclusive to our particular scenario.
>
> We’ve installed ClamAV on a Centos7 server somewhe
Please see other email.
Sent from my iPhone
> On Dec 21, 2018, at 06:15, Claudiu Albu wrote:
>
> Hello all,
>
>
> Been browsing through similar previous occurrences but found nothing
> conclusive to our particular scenario.
>
> We’ve installed ClamAV on a Centos7 server somewhere in
What IP are you coming from? What version ClamAV are you using?
Sent from my iPhone
> On Dec 21, 2018, at 06:27, Claudiu Albu wrote:
>
> Hello all,
>
>
> Been browsing through similar previous occurrences but found nothing
> conclusive to our particular scenario.
>
> We’ve installed C
Hello all,
Been browsing through similar previous occurrences but found nothing
conclusive to our particular scenario.
We’ve installed ClamAV on a Centos7 server somewhere in our infrastructure,
which was supposed to *get its updates through a Squid proxy*.
We’ve set freshclam.conf to *che
Hello all,
Been browsing through similar previous occurrences but found nothing conclusive
to our particular scenario.
We've installed ClamAV on a Centos7 server somewhere in our infrastructure,
which was supposed to get its updates through a Squid proxy.
We've set freshclam.conf to check for
Hello all,
Been browsing through similar previous occurrences but found nothing conclusive
to our particular scenario.
We've installed ClamAV on a Centos7 server somewhere in our infrastructure,
which was supposed to get its updates through a Squid proxy.
We've set freshclam.conf to check for
16 matches
Mail list logo
