Squid3 Antivirus config files
-
Looking forward to this change 8)
-
Good to know. So, there isn't anything we need to do in c-icap.conf or c-icap.magic? Everything is in the squidclamav.conf? I'll just stick to the GUI options for now. Thanks.
-
The screenshot is obviously truncated…
Those fields are greyed out, disabled and empty unless you enable manual configuration.
-
Hopefully finished: https://github.com/pfsense/pfsense-packages/pull/1088
-
Hopefully finished: https://github.com/pfsense/pfsense-packages/pull/1088
I've been
lurkingfollowing the pull requests and your work on github. Very nice job so far, keep up the good work! -
I'm looking to make some changes to stop the "Heuristics.Broken.Executable" issue from coming up but I'm not sure where I would put in the "DetectBrokenExecutables no". Would that go in the squidclamav.conf file?
-
No; that goes to clamd.conf - however, that's the default.
-
That's default now? Nice. The last builds I made were in the 2.1.4s and it had to be put in manually into the clamd.conf. I didn't know if it needed to go in the same place with this package. I'm so glad to be rid of those annoying messages by default now. What is a broken executable? They download and run fine so I'm not sure what is flagging.
-
That's default now
That's always been the default with ClamAV AFAICT.
With this option clamav will try to detect broken executables (both PE and
ELF) and mark them as Broken.Executable.
# Default: no
#DetectBrokenExecutables yesWhat is a broken executable? They download and run fine so I'm not sure what is flagging.
Anything having "broken" PE header.
-
That's always been the default with ClamAV AFAICT.
All I know is that whenever I deploy pfSense with ClamAV then my customers complain about being unable to download files because of the "Heuristics.Broken.Executable" error. If I don't need to go and modify the config file for that anymore I'd be happy. I always seem to forget…