ClamAV: add a warning for the internal message size limit#3341
Conversation
|
Thanks a lot for this follow-up 🚀 ❤️ I have two questions:
|
|
ad 2) The reason for keeping both: The 2GiB warning is different and somehow is only documented in the blog post (at least i could not find any other reference during running my tests). So they are different and for users to make informed decisions we should tell them what's happening. ad 1) Well, i wasn't sure either. ;-) I thought it was MiB, but it seems that for config limits they use SI (M) |
georglauterbach
left a comment
There was a problem hiding this comment.
I see, this is reasonable. If you agree, I'd like to apply some minimal feedback to the changes :)
111a0fa to
4ab3bf0
Compare
4ab3bf0 to
62b6fbf
Compare
Description
ClamAV stops scanning files larger than or equal to 2GiB add a warning for that.
When checking the 4000M limit for CLAMAV_MESSAGE_SIZE_LIMIT in #3332 (comment) i discovered that ClamAV stops scanning at a much lower limit.
Fixes #
Type of change
Checklist:
docs/)Info @wt-io-it