[clamav-users] Some mysterious output from freshclam 0.102.1

Since we still do the quick DNS TXT check (which I described last summer) to determine when to actually run freshclam, we also use the "-v" option on freshclam to get a more detailed log (in case there are still DB sync problems with the BOS mirror). Now, with version 0.102.1, one log (see below)

Re: [clamav-users] Freshclam 0.102.1 ignores "--disable-ipv6"

I looked back in the list a bit, and found some mentions of freshclam and IPv6, but not this issue specifically. The fact that freshclam ignores the "--disable-ipv6" option probably won't be a problem in practice -- as long as the IPv4 connections to ClamAV.net work -- but it is annoying, and clea

Re: [clamav-users] Freshclam 0.102.1 ignores "--disable-ipv6"

I’m fairly certain this was previously discussed. Might want to check the archives. I have not run across any site yet that is IPv6 only, but I suspect users in Asia have. Sent from my iPad -Al- > On Jan 6, 2020, at 18:12, Paul Kosinski via clamav-users > wrote: > > Even though I built

[clamav-users] Freshclam 0.102.1 ignores "--disable-ipv6"

Even though I built the latest ClamAV (0.102.1) with the 'configure' option "--disable-ipv6", freshclam tried using IPv6 addresses when it failed to connect via IPv4 due to a firewall rule (which I now changed to allow port 443 as well as port 80). This rule was part of hardening our mail server

Re: [clamav-users] Manual downloaded virus db file doesn't work

Sorry for the email. I just found that the file that I manually downloaded was incomplete and hence clamscan is reporting the file being invalid. Please ignore my previous email. > On Jan 6, 2020, at 4:24 PM, kaifeng zeng via clamav-users > wrote: > > rnet, but they have access to intranet.

[clamav-users] Manual downloaded virus db file doesn't work

Hi, I have to run clamav in machines that don’t have access to internet, but they have access to intranet. I downloaded the virus db files manually from https://www.clamav.net/downloads and then distribute them to /var/lib/clamav folder in the target machines

Re: [clamav-users] Clamscan taking a very long time

G.W. Haywood wrote: > It's easier to parse logs with 'grep' than it is to tweak the syslog > rule, but aren't we straying from the subject a little? Your logs > should have timestamps, which will tell you what's taking the time. Nope. I give up. No more clamAV for me. Clearly, I'm not smart enou

Re: [clamav-users] Clamscan taking a very long time

Hi there, On Mon, 6 Jan 2020, Michael Newman via clamav-users wrote: G.W. Haywood wrote: ... You might want to look into some of the text processing tools available, such as 'grep'. ... No need for debug or grep. ... I haven't been able to find a way to log only errors and not warnings. I