Hi,
Carlos Williams wrote:
> I am running "Etch" however I would think that it does not matter. I
> commented out the line 41:
>
> PhishingSignatures true
> PhishingScanURLs true
> #PhishingRestrictedScan true
> PhishingAlwaysBlockSSLMismatch false
> PhishingAlwaysBlockCloak false
The new default file doesn't have the "PhishingRestrictedScan true" line at
all:
# grep -ni PhishingRestrictedScan *
clamd.conf.ucf-old:41:PhishingRestrictedScan true
I compared the updated clamd.conf file with my existing one during upgrade
time and decided to go with the current package default. So, perhaps
"PhishingRestrictedScan" shouldn't be used any longer.
# grep -ni Phishing *
clamd.conf:39:PhishingSignatures true
clamd.conf:40:PhishingScanURLs true
clamd.conf:41:PhishingAlwaysBlockSSLMismatch false
clamd.conf:42:PhishingAlwaysBlockCloak false
clamd.conf.ucf-old:39:PhishingSignatures true
clamd.conf.ucf-old:40:PhishingScanURLs true
clamd.conf.ucf-old:41:PhishingRestrictedScan true
clamd.conf.ucf-old:42:PhishingAlwaysBlockSSLMismatch false
clamd.conf.ucf-old:43:PhishingAlwaysBlockCloak false
If you like, I will send you a copy of the new default clamd.conf file
privately (off-list), just let me know.
Checking for "PhishingRestrictedScan" in the example file yeilds no results
either.
/usr/share/doc/clamav-base/examples/clamd.conf
Okay, found some extra information for you, see here:
http://www.nabble.com/PhishingRestrictedScan-is-gone--td18332907.html
There is a solution by Edwin to effectively get the same behaviour as you
had before as well.
Kind Regards
AndrewM
Andrew McGlashan
Broadband Solutions now including VoIP
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
