[clamav-users] ClamAV 0.103.8 on Ubuntu 22.04.2 LTS

Hi @ all, today has arrived ClamAV in version 0.103.8 for Ubuntu 22.04.2 (as System update over the Ubuntu Store App). Which files comes exactly with this update? Please check the attached screenshot kind regards @ all Marc___ Manage your clamav-user

[clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

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

Re: [clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

why you have set two times the "PrivateMirror" with identically IP's? Can't believe that this happens with the automated PostInst 😉 Von / From: Clamav User Mailinglist An / To: Newcomer01 CC / CC: Kevin O'connor

Re: [clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

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

Re: [clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

i would suggest, to delete alle libraries in /var/lib/clamav and download all complete new. CLD Files comes not regularly, normally we have CVD only. If i understand this well, CLD Files comes only when error occures while updating. https:/blog.clamav.net/2021/03/clamav-cvds-cdiffs-and-magic-be

Re: [clamav-users] 0 length bytecode.cvd causing problems with clamav daemon

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

[clamav-users] What was detected?

Got an email marked as infected by clamav. I cannot determine what was detected. A long time ago I asked here and someone described how to scan an individual email file, log the results and scan the log for what was detected. Or maybe clued me in on which log I was not searching properly.

Re: [clamav-users] What was detected?

On 2/27/2023 3:47 PM, joe a wrote: Got an email marked as infected by clamav.  I cannot determine what was detected. A long time ago I asked here and someone described how to scan an individual email file, log the results and scan the log for what was detected.   Or maybe clued me in on which

Re: [clamav-users] What was detected?

On 2/27/2023 3:52 PM, joe a wrote: On 2/27/2023 3:47 PM, joe a wrote: Got an email marked as infected by clamav.  I cannot determine what was detected. A long time ago I asked here and someone described how to scan an individual email file, log the results and scan the log for what was detec

Re: [clamav-users] What was detected?

On 27/02/2023 20:57, joe a wrote: On 2/27/2023 3:52 PM, joe a wrote: On 2/27/2023 3:47 PM, joe a wrote: Got an email marked as infected by clamav.  I cannot determine what was detected. A long time ago I asked here and someone described how to scan an individual email file, log the results

Re: [clamav-users] What was detected?

On 2/27/2023 4:24 PM, Paul Netpresto wrote: On 27/02/2023 20:57, joe a wrote: On 2/27/2023 3:52 PM, joe a wrote: On 2/27/2023 3:47 PM, joe a wrote: Got an email marked as infected by clamav.  I cannot determine what was detected. A long time ago I asked here and someone described how to sca

Re: [clamav-users] What was detected?

On 27/02/2023 21:33, joe a wrote: On 2/27/2023 4:24 PM, Paul Netpresto wrote: On 27/02/2023 20:57, joe a wrote: On 2/27/2023 3:52 PM, joe a wrote: On 2/27/2023 3:47 PM, joe a wrote: Got an email marked as infected by clamav.  I cannot determine what was detected. A long time ago I asked h

Re: [clamav-users] What was detected?

On Mon, 27 Feb 2023, joe a wrote: 66 On 2/27/2023 4:24 PM, Paul Netpresto wrote: I attempted that just now. Ran clamscan --debug -f some-email.eml After it cranks up and apparently beings actually scanning the email, starts cranking out errors/warnings like: Return-path: : No such file or d

Re: [clamav-users] What was detected?

On 2/27/2023 4:49 PM, Andrew C Aitchison via clamav-users wrote: On Mon, 27 Feb 2023, joe a wrote: 66 On 2/27/2023 4:24 PM, Paul Netpresto wrote: I attempted that just now.  Ran clamscan --debug -f some-email.eml After it cranks up and apparently beings actually scanning the email, starts cra

[clamav-users] about ClamAV 0.103.8, 0.105.2 and 1.0.1 patch versions published

Hello. I have question. Does the information in the following URL affect even if the NAS file system is BTRFS? Will it be affected even if the client uses HFS or dmg? https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html ___ Manage your

Re: [clamav-users] about ClamAV 0.103.8, 0.105.2 and 1.0.1 patch versions published

On 28.02.23 12:41, takahiro suzuki via clamav-users wrote: Does the information in the following URL affect even if the NAS file system is BTRFS? since the patches only mengion DMS files and HFS+ files, I don't see any reason they should affect BTRFS filesystems. Will it be affected even i