Hello, everyone. I understand how I can increase the max file size for command line or clamd scanning. But I also see many references to possible severe system damage that could occur by scanning large files. The clamd.conf file explicitly warns against setting several limits too high. I have searched the FAQ, the documentation PDF, the list archive files, and have spent significant time on general internet searching; however, I can find no reference anywhere to what that damage could be other than increased risk of DDoS attacks being successful if email is being automatically scanned.
I have another solution for email scanning, so clamav would only be used for scanning individual files on the command line or via clamd with Python and Perl scripts. So what damage could occur other than resource consumption by the individual scans on larger files? I've scanned files as large at 2GB with no issues whatsoever and I am just curious as to what the issues would be. Regards, Jay ________________________________ Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
_______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
