[clamav-users] LibClamAV Warning: RWX mapping denied

[Tilman Schmidt]

This morning, a bunch of RHEL6 systems greeted me with mails saying:

/etc/cron.daily/freshclam:

ERROR: During database load : LibClamAV Warning: RWX mapping denied:
Can't allocate RWX Memory: Permission denied

I found an old Red Hat Bugzilla entry (Bug 1172774) for Fedora 21 which
was closed as fixed by an selinux-policy update on 2015-08-14.
However the systems in question have been running for two years with
that configuration.

This is RHEL6 with the ClamAV packages from EPEL:

clamav-0.99.4-1.el6.x86_64
clamav-db-0.99.4-1.el6.x86_64
clamd-0.99.4-1.el6.x86_64

Why would freshclam suddenly trigger that message now?

Thanks,
Tilman
___
clamav-users mailing list
clamav-users@lists.clamav.net
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

Re: [clamav-users] We STILL cannot reliably get virus updates (since new mirrors)

[Paul Kosinski]

Last night our new method of getting cvd updates showed that it was
*one hour* from the time the DNS TXT record claimed a new cvd was
available to the time when our quick curl said it was really available!

In particular at 1:03 AM (EDT), DNS said version 24739 was available,
but a curl of the first few bytes of the cvd file said it was still at
version 24738. It wasn't until 2:03 AM that curl reported that version
24739 was really available for download.

Log file excerpt follows. (Comment lines beginning '#' added be me.)


--  Tuesday 10 July 2018 at 00:48:01  
--

/opt/clamav/bin/testclam-external
-->  DNS  D 24738/24738  B 324/324  M 58/58

#   ^ ^
#   DNS   local

--  Tuesday 10 July 2018 at 01:03:01  
--

/opt/clamav/bin/testclam-external
-->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58

#   ^ ^ ^
#   curl  DNS   local

--  Tuesday 10 July 2018 at 01:18:01  
--

/opt/clamav/bin/testclam-external
-->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58


--  Tuesday 10 July 2018 at 01:33:01  
--

/opt/clamav/bin/testclam-external
-->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58


--  Tuesday 10 July 2018 at 01:48:01  
--

/opt/clamav/bin/testclam-external
-->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58


--  Tuesday 10 July 2018 at 02:03:01  
--

/opt/clamav/bin/testclam-external
-->  UPD  D 24739/24739/24738  B 324/324/324  M 58/58/58

#   ^ ^ ^
#   curl  DNS   local

removed `/opt/clamav/share/clamav/mirrors.dat'
/opt/clamav/bin/freshclam -v --stdout --on-update-execute=EXIT_1
Current working dir is /opt/clamav.d/clamav.0.100.0/share/clamav
Max retries == 1
ClamAV update process started at Tue Jul 10 02:03:03 2018
Using IPv6 aware code
Querying current.cvd.clamav.net
TTL: 1798
Software version from DNS: 0.100.1
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.100.0 Recommended version: 0.100.1
DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
main.cvd version from DNS: 58
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: 
sigmgr)
daily.cvd version from DNS: 24739
Retrieving http://database.clamav.net/daily.cvd
Using ip '10.11.14.160' for fetching.
Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.189.138)
Downloading daily.cvd [100%]
Loading signatures from daily.cvd
Properly loaded 2008906 signatures from new daily.cvd
daily.cvd updated (version: 24739, sigs: 2008906, f-level: 63, builder: neo)
Querying daily.24739.91.1.0.6810BD8A.ping.clamav.net
bytecode.cvd version from DNS: 324
bytecode.cvd is up to date (version: 324, sigs: 89, f-level: 63, builder: neo)
Database updated (6575244 signatures) from database.clamav.net (IP: 
104.16.189.138)
OnUpdateExecute: EXIT_1

--  Tuesday 10 July 2018 at 02:03:17  
--
___
clamav-users mailing list
clamav-users@lists.clamav.net
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

Re: [clamav-users] Bytecode 86 failed to run

[Alain Zidouemba]

This issue should be resolved now. If the issue persists for you, let us
know.

- Alain

On Mon, Jul 9, 2018 at 12:14 AM,  wrote:

> On my debian 9, clamav 0.100.0+dfsg-0+deb8u1) I got following error:
>
> clamscan /media/6b300944-6e7c-493e-b9c9-faeebb70a415/nastenka
> /srv/dev-disk-by-label-white/zaloha '--exclude=\.(mp4|MP4|mkv|MKV|
> avi|AVI|wmv|WMV|ts|TS|flv|FLV|mov|MOV|JPG|jpg|mp3|MP3|tc)$' -ri -l
> /var/log/clamav/clamscanDisk.log
> LibClamAV Warning: [Bytecode JIT]: recovered from error
> LibClamAV Warning: [Bytecode JIT]: JITed code intercepted runtime error!
> LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
> LibClamAV Warning: Bytecode 86 failed to run: Time limit reached
> LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
> LibClamAV Warning: [Bytecode JIT]: recovered from error
> LibClamAV Warning: [Bytecode JIT]: JITed code intercepted runtime error!
> LibClamAV Warning: Bytecode 86 failed to run: Time limit reached
> LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
> LibClamAV Warning: [Bytecode JIT]: recovered from error
> LibClamAV Warning: [Bytecode JIT]: JITed code intercepted runtime error!
> LibClamAV Warning: Bytecode 86 failed to run: Time limit reached
> LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
> LibClamAV Warning: [Bytecode JIT]: recovered from error
> LibClamAV Warning: [Bytecode JIT]: JITed code intercepted runtime error!
> LibClamAV Warning: Bytecode 86 failed to run: Time limit reached
> LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
> LibClamAV Warning: [Bytecode JIT]: recovered from error
> LibClamAV Warning: [Bytecode JIT]: JITed code intercepted runtime error!
> LibClamAV Warning: Bytecode 86 failed to run: Time limit reached
> LibClamAV Warning: [Bytecode JIT]: Bytecode run timed out, timeout flag set
> LibClamAV Warning: [Bytecode JIT]: recovered from error
> LibClamAV Warning: [Bytecode JIT]: JITed code intercepted runtime error!
> LibClamAV Warning: Bytecode 86 failed to run: Time limit reached
>
> in clamd.conf is:
> Bytecode true
> BytecodeSecurity TrustSigned
> BytecodeTimeout 12
>
> There is no clamd, I do not need it. I just need once a week check discs.
>
> Thank you for help.
>
>
>
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> 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
clamav-users@lists.clamav.net
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] clamav-milter with sendmail on Fedora 28: init failed to open, to error state, initialization failed, temp failing commands

[Robert Kudyba]

Hello hive,

Running:
clamav-0.100.0-2.fc28.x86_64

clamd, freshclam and clamav-milter all up and running:
ps -auwx | grep clam
clamupd+ 20336  0.0  0.0  50672  4016 ?Ss   Jun29   1:15
/usr/bin/freshclam -d -c 4
clamav   23713  0.0  0.0 176780  1160 ?Ssl  13:23   0:00
/usr/sbin/clamav-milter -c /etc/mail/clamav-milter.conf
clamscan 25458  0.0  4.6 1405848 1142996 ? Ssl  13:27   0:00
/usr/sbin/clamd -c /etc/clamd.d/scan.conf
root 25593  0.0  0.0   9156  1084 pts/1S+   17:02   0:00 grep
--color=auto clam

However it fails with sendmail with these errors:
Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273:
milter_sys_read(clamav): cmd read returned 11, expecting 1431194445
Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter (clamav): to
error state
Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter (clamav):
init failed to open
Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter (clamav): to
error state
Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter:
initialization failed, temp failing commands

Here's the relevant line in sendmail.mc:
INPUT_MAIL_FILTER(`clamav', `S=local:/var/run/clamd.scan/clamd.sock,
F=T,T=S:4m;R:4m;E:10m')dnl

Lines in /etc/mail/clamav-milter.conf
MilterSocket /var/run/clamav-milter/clamav-milter.socket
MilterSocket inet:7357
ClamdSocket tcp:localhost:3310
ClamdSocket unix:/var/run/clamd.scan/clamd.sock

Lines in /etc/clamd.d/scan.conf

TCPSocket 3310
TCPAddr 127.0.0.1

Everything I've read says that as long as ClamdSocket in the
clamav-milter.conf and INPUT_MAIL_FILTER in sendmail.mc match it should
work.

Is my syntax wrong some where?
___
clamav-users mailing list
clamav-users@lists.clamav.net
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

Re: [clamav-users] We STILL cannot reliably get virus updates (since new mirrors)

[Joel Esler (jesler)]

Thanks for this feedback everyone.  This is extremely useful.


> On Jul 10, 2018, at 11:26 AM, Paul Kosinski  wrote:
> 
> Last night our new method of getting cvd updates showed that it was
> *one hour* from the time the DNS TXT record claimed a new cvd was
> available to the time when our quick curl said it was really available!
> 
> In particular at 1:03 AM (EDT), DNS said version 24739 was available,
> but a curl of the first few bytes of the cvd file said it was still at
> version 24738. It wasn't until 2:03 AM that curl reported that version
> 24739 was really available for download.
> 
> Log file excerpt follows. (Comment lines beginning '#' added be me.)
> 
> 
> --  Tuesday 10 July 2018 at 00:48:01  
> --
> 
> /opt/clamav/bin/testclam-external
> -->  DNS  D 24738/24738  B 324/324  M 58/58
> 
> #   ^ ^
> #   DNS   local
> 
> --  Tuesday 10 July 2018 at 01:03:01  
> --
> 
> /opt/clamav/bin/testclam-external
> -->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58
> 
> #   ^ ^ ^
> #   curl  DNS   local
> 
> --  Tuesday 10 July 2018 at 01:18:01  
> --
> 
> /opt/clamav/bin/testclam-external
> -->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58
> 
> 
> --  Tuesday 10 July 2018 at 01:33:01  
> --
> 
> /opt/clamav/bin/testclam-external
> -->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58
> 
> 
> --  Tuesday 10 July 2018 at 01:48:01  
> --
> 
> /opt/clamav/bin/testclam-external
> -->  EXT  D 24738/24739/24738  B 324/324/324  M 58/58/58
> 
> 
> --  Tuesday 10 July 2018 at 02:03:01  
> --
> 
> /opt/clamav/bin/testclam-external
> -->  UPD  D 24739/24739/24738  B 324/324/324  M 58/58/58
> 
> #   ^ ^ ^
> #   curl  DNS   local
> 
> removed `/opt/clamav/share/clamav/mirrors.dat'
> /opt/clamav/bin/freshclam -v --stdout --on-update-execute=EXIT_1
> Current working dir is /opt/clamav.d/clamav.0.100.0/share/clamav
> Max retries == 1
> ClamAV update process started at Tue Jul 10 02:03:03 2018
> Using IPv6 aware code
> Querying current.cvd.clamav.net
> TTL: 1798
> Software version from DNS: 0.100.1
> WARNING: Your ClamAV installation is OUTDATED!
> WARNING: Local version: 0.100.0 Recommended version: 0.100.1
> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
> main.cvd version from DNS: 58
> main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: 
> sigmgr)
> daily.cvd version from DNS: 24739
> Retrieving http://database.clamav.net/daily.cvd
> Using ip '10.11.14.160' for fetching.
> Trying to download http://database.clamav.net/daily.cvd (IP: 104.16.189.138)
> Downloading daily.cvd [100%]
> Loading signatures from daily.cvd
> Properly loaded 2008906 signatures from new daily.cvd
> daily.cvd updated (version: 24739, sigs: 2008906, f-level: 63, builder: neo)
> Querying daily.24739.91.1.0.6810BD8A.ping.clamav.net
> bytecode.cvd version from DNS: 324
> bytecode.cvd is up to date (version: 324, sigs: 89, f-level: 63, builder: neo)
> Database updated (6575244 signatures) from database.clamav.net (IP: 
> 104.16.189.138)
> OnUpdateExecute: EXIT_1
> 
> --  Tuesday 10 July 2018 at 02:03:17  
> --
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> 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
clamav-users@lists.clamav.net
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

Re: [clamav-users] clamav-milter with sendmail on Fedora 28: init failed to open, to error state, initialization failed, temp failing commands

[Kees Theunissen]

On Tue, 10 Jul 2018, Robert Kudyba wrote:

>Hello hive,
>
>Running:
>clamav-0.100.0-2.fc28.x86_64
>
>clamd, freshclam and clamav-milter all up and running:
>ps -auwx | grep clam
>clamupd+ 20336  0.0  0.0  50672  4016 ?Ss   Jun29   1:15
>/usr/bin/freshclam -d -c 4
>clamav   23713  0.0  0.0 176780  1160 ?Ssl  13:23   0:00
>/usr/sbin/clamav-milter -c /etc/mail/clamav-milter.conf
>clamscan 25458  0.0  4.6 1405848 1142996 ? Ssl  13:27   0:00
>/usr/sbin/clamd -c /etc/clamd.d/scan.conf
>root 25593  0.0  0.0   9156  1084 pts/1S+   17:02   0:00 grep
>--color=auto clam
>
>However it fails with sendmail with these errors:
>Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273:
>milter_sys_read(clamav): cmd read returned 11, expecting 1431194445
>Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter (clamav): to
>error state
>Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter (clamav):
>init failed to open
>Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter (clamav): to
>error state
>Jul 10 17:03:45 storm sendmail[26273]: w6AL3j2R026273: Milter:
>initialization failed, temp failing commands
>
>Here's the relevant line in sendmail.mc:
>INPUT_MAIL_FILTER(`clamav', `S=local:/var/run/clamd.scan/clamd.sock,
>F=T,T=S:4m;R:4m;E:10m')dnl


Your INPUT_MAIL_FILTER should be clamav-milter listening on socket
/var/run/clamav-milter/clamav-milter.socket (as defined below)
and not the clamd daemom which is listening on socket
/var/run/clamd.scan/clamd.sock


>
>Lines in /etc/mail/clamav-milter.conf
>MilterSocket /var/run/clamav-milter/clamav-milter.socket
>MilterSocket inet:7357
>ClamdSocket tcp:localhost:3310
>ClamdSocket unix:/var/run/clamd.scan/clamd.sock
>
>Lines in /etc/clamd.d/scan.conf
>
>TCPSocket 3310
>TCPAddr 127.0.0.1
>
>Everything I've read says that as long as ClamdSocket in the
>clamav-milter.conf and INPUT_MAIL_FILTER in sendmail.mc match it should
>work.
>
>Is my syntax wrong some where?
>



Regards,

Kees Theunissen.

-- 
Kees Theunissen,  System and network manager,   Tel: +31 (0)40-3334724
Dutch Institute For Fundamental Energy Research (DIFFER)
email address:c.j.theunis...@differ.nl
postal address:   PO Box 6336, 5600 HH, Eindhoven, the Netherlands
visitors address: De Zaale 20, 5612 AJ, Eindhoven, the Netherlands

___
clamav-users mailing list
clamav-users@lists.clamav.net
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

Re: [clamav-users] We STILL cannot reliably get virus updates (since new mirrors)

[Paul Kosinski]

I have a question. I presume that there are more physical Cloudflare 
server instances than implied by database.clamav.net's 5 IP addresses,
and that they are geographically distributed, rather than all being
in/near San Francisco. This suggests that they are Anycast addresses.
But I don't know how to determine where the server instances are
located, or which one(s) we reach when trying to download cvds.

The fact that we have observed a 1 hour delay further suggests that
there a large number of instances, otherwise they would be brought into
sync with the DNS TXT record more quickly. Is there any way that you
people at ClamAV can determine when the various server instances in fact
get the new cvd files? I would think that a CDN would provide statistics
on that, especially if expected delays are spelled out in an SLA.


On Tue, 10 Jul 2018 22:11:46 +
"Joel Esler (jesler)"  wrote:

> Thanks for this feedback everyone.  This is extremely useful.
> 
> 
> > On Jul 10, 2018, at 11:26 AM, Paul Kosinski
> >  wrote:
> > 
> > Last night our new method of getting cvd updates showed that it was
> > *one hour* from the time the DNS TXT record claimed a new cvd was
> > available to the time when our quick curl said it was really
> > available!
> > 
> > In particular at 1:03 AM (EDT), DNS said version 24739 was
> > available, but a curl of the first few bytes of the cvd file said
> > it was still at version 24738. It wasn't until 2:03 AM that curl
> > reported that version 24739 was really available for download.

> 
___
clamav-users mailing list
clamav-users@lists.clamav.net
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

Re: [clamav-users] We STILL cannot reliably get virus updates (since new mirrors)

[Freddie Cash]

Joel posted pictures (in one of these update thread) of where the mirrors
are located along with the relative traffic that each one transfers.

Cheers,
Freddie

Typos courtesy of my phone's keyboard.

On Tue, Jul 10, 2018, 6:37 PM Paul Kosinski,  wrote:

> I have a question. I presume that there are more physical Cloudflare
> server instances than implied by database.clamav.net's 5 IP addresses,
> and that they are geographically distributed, rather than all being
> in/near San Francisco. This suggests that they are Anycast addresses.
> But I don't know how to determine where the server instances are
> located, or which one(s) we reach when trying to download cvds.
>
> The fact that we have observed a 1 hour delay further suggests that
> there a large number of instances, otherwise they would be brought into
> sync with the DNS TXT record more quickly. Is there any way that you
> people at ClamAV can determine when the various server instances in fact
> get the new cvd files? I would think that a CDN would provide statistics
> on that, especially if expected delays are spelled out in an SLA.
>
>
> On Tue, 10 Jul 2018 22:11:46 +
> "Joel Esler (jesler)"  wrote:
>
> > Thanks for this feedback everyone.  This is extremely useful.
> >
> >
> > > On Jul 10, 2018, at 11:26 AM, Paul Kosinski
> > >  wrote:
> > >
> > > Last night our new method of getting cvd updates showed that it was
> > > *one hour* from the time the DNS TXT record claimed a new cvd was
> > > available to the time when our quick curl said it was really
> > > available!
> > >
> > > In particular at 1:03 AM (EDT), DNS said version 24739 was
> > > available, but a curl of the first few bytes of the cvd file said
> > > it was still at version 24738. It wasn't until 2:03 AM that curl
> > > reported that version 24739 was really available for download.
>
> >
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net
> 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
clamav-users@lists.clamav.net
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

Re: [clamav-users] We STILL cannot reliably get virus updates (since new mirrors)

[Eric Tykwinski]

They have some documentation on their site: 
https://support.cloudflare.com/hc/en-us/articles/115000540888-Load-Balancing-Geographic-Regions
 

No clue what regions they are using, but hopefully they donated some, it’s a 
pretty solid anycast system.

Sincerely,

Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300

> On Jul 10, 2018, at 10:03 PM, Freddie Cash  wrote:
> 
> Joel posted pictures (in one of these update thread) of where the mirrors are 
> located along with the relative traffic that each one transfers.
> 
> Cheers,
> Freddie
> 
> Typos courtesy of my phone's keyboard.
> 
> On Tue, Jul 10, 2018, 6:37 PM Paul Kosinski,  > wrote:
> I have a question. I presume that there are more physical Cloudflare 
> server instances than implied by database.clamav.net 
> 's 5 IP addresses,
> and that they are geographically distributed, rather than all being
> in/near San Francisco. This suggests that they are Anycast addresses.
> But I don't know how to determine where the server instances are
> located, or which one(s) we reach when trying to download cvds.
> 
> The fact that we have observed a 1 hour delay further suggests that
> there a large number of instances, otherwise they would be brought into
> sync with the DNS TXT record more quickly. Is there any way that you
> people at ClamAV can determine when the various server instances in fact
> get the new cvd files? I would think that a CDN would provide statistics
> on that, especially if expected delays are spelled out in an SLA.
> 
> 
> On Tue, 10 Jul 2018 22:11:46 +
> "Joel Esler (jesler)" mailto:jes...@cisco.com>> wrote:
> 
> > Thanks for this feedback everyone.  This is extremely useful.
> > 
> > 
> > > On Jul 10, 2018, at 11:26 AM, Paul Kosinski
> > > mailto:clamav-us...@iment.com>> wrote:
> > > 
> > > Last night our new method of getting cvd updates showed that it was
> > > *one hour* from the time the DNS TXT record claimed a new cvd was
> > > available to the time when our quick curl said it was really
> > > available!
> > > 
> > > In particular at 1:03 AM (EDT), DNS said version 24739 was
> > > available, but a curl of the first few bytes of the cvd file said
> > > it was still at version 24738. It wasn't until 2:03 AM that curl
> > > reported that version 24739 was really available for download.
> 
> > 
> ___
> clamav-users mailing list
> clamav-users@lists.clamav.net 
> 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
> clamav-users@lists.clamav.net
> 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
clamav-users@lists.clamav.net
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

Re: [clamav-users] We STILL cannot reliably get virus updates (since new mirrors)

[Paul Kosinski]

I looked at a bunch of pages on Cloudflare's site. What they offer is
quite impressive -- way beyond "mere" distributed/anycast CDN.


On Tue, 10 Jul 2018 22:13:49 -0400
Eric Tykwinski  wrote:

> They have some documentation on their site:
> https://support.cloudflare.com/hc/en-us/articles/115000540888-Load-Balancing-Geographic-Regions
> 
> No clue what regions they are using, but hopefully they donated some,
> it’s a pretty solid anycast system.
> 
> Sincerely,
> 
> Eric Tykwinski
> TrueNet, Inc.
> P: 610-429-8300
> 
> > On Jul 10, 2018, at 10:03 PM, Freddie Cash 
> > wrote:
> > 
> > Joel posted pictures (in one of these update thread) of where the
> > mirrors are located along with the relative traffic that each one
> > transfers.
> > 
> > Cheers,
> > Freddie
> > 
> > Typos courtesy of my phone's keyboard.

___
clamav-users mailing list
clamav-users@lists.clamav.net
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