Hello! and thank you for your help. Here are the answers:
(a) your version of ClamAV: Version 0.103.0.
(b) how and when it was installed: was installing using custombuild
scripts from Directa Admin control panel.
(c) exactly which databases you are using: ClamAV 0.103.0/26016/Sun Dec
13 15:3
Okay, so then it seems like 1) ClamAV’s origin server periodically serves an
old version of a file after the DNS TXT record is updated, or 2) Cloudflare
returns a cached resource from the wrong URL, or 3) Someone is making a request
to new ?version URLs before the DNS TXT record is updated (and
I did a quick grep on the the source code (and compiled output too) of
ClamAV 0.103.0, and I couldn't find any instance of 'CF-Cache-Status'.
Should freshclam (or somebody) be checking this HTTP header line that
Cloudflare returns? The 'STALE' and 'UPDATING' values sound like they
might be particul
Both of those things are done as well.
Sent from my iPhone
> On Dec 13, 2020, at 19:24, Dave Warren via clamav-users
> wrote:
>
> On 2020-12-11 08:51, Paul Kosinski via clamav-users wrote:
>> "The whole CVD filename is not versioned (always "daily.cvd") which is
>> why the CloudFlare cach
On 2020-12-11 08:51, Paul Kosinski via clamav-users wrote:
"The whole CVD filename is not versioned (always "daily.cvd") which is
why the CloudFlare caching issue may result in serving the previous
version."
HTML filenames for Web pages are not versioned either. Does this mean
that CDNs like Clo
Hi there,
On Sun, 13 Dec 2020, Aitor Serra Martín wrote:
I'm getting this error all the time with complete scans:
LibClamAV Error: [scan_biff_for_xlm_macros] Unexpected state value 4
...
NAME="CloudLinux"
...
This message is emitted by the function scan_biff_for_xlm_macros() in
.../libclamav
