Presumably it was added as an exaggeration to discourage people from setting it too high and then complaining about undefined behavior. My expectation is that anything over 2GB may not scan correctly because clamav wasn’t written to handle large files and thus the variables used for storing file sizes and offsets are inconsistent throughout the codebase. My personal recommendation is to not set MaxScanSize or MaxFileSize higher than 2GB.
Outside of that, the only consequence I’m aware for scanning very large files is very long scan times and perhaps very high RAM usage. -Micah From: clamav-users <clamav-users-boun...@lists.clamav.net> On Behalf Of ron ron via clamav-users Sent: Friday, November 27, 2020 8:14 AM To: clamav-users@lists.clamav.net Cc: ron ron <ron700...@gmail.com> Subject: [clamav-users] clam scan.conf meaning of severe damage to the system in /etc/clam.d/scan.conf there is this for many settings (MaxScanSize=150M for example) # Note: disabling this limit or setting it too high may result in severe damage to the system. What is severe damage? - it causes linux to corrupt itself, where I need to reinstall linux? - it somehow causes irreparable damage to a hard disk or ssd or RAM? - it causes the cpu or motherboard to fail? Can the reason for this statement of severe damage be further clarified and explained? If I set MaxScanSize to 151M is that good or bad and why? does this scan.conf also affect doing a manual "clamscan --recursive /"
_______________________________________________ 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
