Scott Beck wrote: > Hi, > > Another note on this issue. Someone just reported that without the > CL_SCAN_PHISHING_DOMAINLIST option set they are seeing libclamav hang. > Please consider adding this to CL_SCAN_STDOPT or remove the option and > turn it on internally always or reverse the option and have something > like CL_SCAN_PHISHING_NODOMAINLIST.
Yup. That'd be me. (thanks for re-reporting it here, Scott; and thanks for your help figuring it out) On the one hand, tracking this down helped me learn a lot more about ClamAV, and the various options... I was able to refine and streamline my code quite a bit, and eliminate various things I didn't actually need to do. But ... for all that I value learning experiences, I would like to strongly make one statement: The default behavior of clamscan should match the "standard options". If clamscan/clamdscan, by default, does CL_SCAN_PHISHING_DOMAINLIST, then that should be in CL_SCAN_STDOPT. Anything else that clamscan/clamdscan do by default should also be in CL_SCAN_STDOPT. Anything that clamscan/clamdscan don't do by default should NOT be in CL_SCAN_STDOPT (though I don't think anything falls into that category). If you're going to not add CL_SCAN_PHISHING_DOMAINLIST to CL_SCAN_STDOPT, then stop having clamscan/clamdscan use it by default. Make it a command-line option. (though, my recommendation is: add CL_SCAN_PHISHING_DOMAINLIST to CL_SCAN_STDOPT ... I agree with Scott that it's a useful and necessary function) _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
