In message <[EMAIL PROTECTED]> Nigel Horne <[EMAIL PROTECTED]> wrote:
>Ignasi Prat wrote: >> Hi Nigel. >> >> Testing 2006-09-18 build I encountered three things that I think I >> should mention: >> >> 1) Freshclam still gives always "WARNING: Invalid DNS reply. Falling >> back to HTTP mode." I assume you are still working on the dns patch for >> freshclam. > >Mark has sent a fix to his patch which I'll test and upload ASAP. I'm not seeing that here... Am I missing something? -------------------------------------- Current working dir is C:\Progra~1\clamAV\data Max retries == 3 ClamAV update process started at Wed Sep 20 10:32:59 2006 SECURITY WARNING: NO SUPPORT FOR DIGITAL SIGNATURES See the FAQ at http://www.clamav.net/faq.html for an explanation. TTL: 879 Software version from DNS: 0.88.4 main.cvd version from DNS: 40 main.cvd is up to date (version: 40, sigs: 64138, f-level: 8, builder: tkojm) daily.cvd version from DNS: 1911 daily.cvd is up to date (version: 1911, sigs: 6073, f-level: 8, builder: ccordes) >> 2) Clamd and clamscan always claim database is older than 7 days when >> freshclam does not update database (because it is up to date) just after >> a fresh install. This is not a problem, just a cosmetic issue that is >> automatically solved the first time freshclam needs to update database. >> In my case I just deleted files in data and called freshclam and after >> that all was fine. > >That's because I don't always put the latest signatures in to the >distribution file. That's fair -- Is there a need to include any definitions, since they'll tend to be out of date anyway? Or if you are, would it be worth including the /test/ files? >> 3) Clamd is never notified by freshclam, because it claims: [WARNING: >> Clamd was NOT notified: Can't find or parse configuration file "C:\Prog >> ram]. In readme says this message means daily and main are not in >> documents and settings ¿? what relation has this which clamd being >> notified ? > >That is a bug in freshclam. The bug is not Windows specific. Is it? It looks to me like LFN/SFN issue, if I use NotifyClamd SFN C:\Progra~1\ClamAV\conf\clamd.conf Then my freshclam.log looks good: -------------------------------------- ClamAV update process started at Wed Sep 20 10:24:26 2006 SECURITY WARNING: NO SUPPORT FOR DIGITAL SIGNATURES See the FAQ at http://www.clamav.net/faq.html for an explanation. main.cvd is up to date (version: 40, sigs: 64138, f-level: 8, builder: tkojm) Downloading daily.cvd [100] daily.cvd updated (version: 1911, sigs: 6073, f-level: 8, builder: ccordes) Database updated (70211 signatures) from db.US.clamav.net (IP: 193.1.193.64) Clamd successfully notified about the update. And ClamD notices too... -- Dave Warren, MSN Instant Messenger: [EMAIL PROTECTED] Phone: (204) 480-8407 Toll free: (888) 371-3470 Fax: (204) 283-6028 _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-win32
