Hello,
Le 07/04/2019 à 18:18, G.W. Haywood via clamav-users a écrit :
Hi there,
On Sun, 7 Apr 2019, Maarten Broekman wrote:
Given that the PhishTank signatures, specifically, have been causing the
performance issues, no. It's not unreasonable to want to pull them, and
only them, out. Having them in a separate db file would be highly
beneficial to those of us that don't want or need them at all. Barring
that, having a configuration option to disable them that is separate
from
heuristics and safebrowsing would be just as effective.
How about something like
grep -a '^Phishtank.Phishing' daily.cld | cut -d':' -f1 >
~/phishtank.ign2
This is not optimized :
Phishtank.Phishing are loaded in memory.
Then phishtank.ign2 is loaded on memory.
So there is a lot of memory used for nothing. And I guess this will slow
down the scan.
... and one day I created a *huge* ign2 file and it crashed clamd. Ign2
files may not be appropriate to ignore tons of signatures.
--
Cordialement / Best regards,
Arnaud Jacques
Gérant de SecuriteInfo.com
Téléphone : +33-(0)3.44.39.76.46
E-mail : a...@securiteinfo.com
Site web : https://www.securiteinfo.com
Facebook : https://www.facebook.com/pages/SecuriteInfocom/132872523492286
Twitter : @SecuriteInfoCom
Securiteinfo.com
La Sécurité Informatique - La Sécurité des Informations.
266, rue de Villers
60123 Bonneuil en Valois
_______________________________________________
clamav-users mailing list
clamav-users@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
