Thank you, Robert,
I'm not sure how I managed to misread 1.0.3 for 0.103. My apologies.
Kevin
On Wed, Oct 25, 2023 at 5:15 PM Robert M. Stockmann via clamav-users <
clamav-users@lists.clamav.net> wrote:
> On Wed, 25 Oct 2023, Kevin O'Connor via clamav-users wrote:
>
> &g
Hi Micah,
I'm assuming that this is the report of an updated 0.103.11:
$ /usr/sbin/clamd --version
ClamAV 1.0.3/27072/Wed Oct 25 07:45:37 2023
Is that correct?.. it was difficult to tell from the links.
Kevin
On Wed, Oct 25, 2023 at 2:13 PM Micah Snyder (micasnyd) via clamav-users <
clamav-us
a bytecode.cld.
>
> If that's not the case, then we may have a bug in freshclam and I would
> love some more information on what freshclam is downloading when it runs
> in order to get into this strange state.
>
> Best,
> Micah
>
> Micah Snyder
> ClamAV Developm
Marc,
I had a similar understanding of that document. That is; if there is no
bytecode.cvd pushed by the ClamAV team, it should not exist on my local
scanners. When I checked the mirror and there was no bytecode.cvd file, yet
it appeared on my scanner machines with 0 length, I figured that the ne
Heh, good question. Just checked again, and it looks like that was a
copy-paste error. There is only one PrivateMirror line.
Kevin
On Mon, Feb 27, 2023 at 12:02 PM newcomer01 via clamav-users <
clamav-users@lists.clamav.net> wrote:
> why you have set two times the "PrivateMirror" with identical
I am having an issue with 0 length bytecode.cvd files on my scanner
instances. This seems to have started sometime on 22 Feb, I'm afraid I
don't have an exact time. The clamav daemon produces logs like the
following:
Feb 27 14:39:11 av-scan-wrhn clamd[163614]: LibClamAV Error: cli_cvdverify:
Can
