Exceptions are made in their clamd.conf or command line for clamscan.
Where to quarantine is also made at the above.
AutoScanning requires a third party application as BSD doesn’t support clamonacc, so I would recommend fswatch:
So depending on your use case, I personally use a clamdscan plist for each user which launches fswatch to run a clamdscan on each user's access to a file on login.
You can also schedule a clamscan for specific directories to the whole server on a crontab.
My biggest hurdle which I couldn’t figure out was how to notify users when a suspect file was quarantined, as macOS has limitations on who can call the Notification library, but nothing to do with ClamAV.
My work around was just writing to file in the the Documents directory, which also Quarantined to a ~/Documents/Quarantine/ directory so if a file simple went missing I would know where it was from and where it went to.
P.S. Have a good new year everyone...
Sincerely,
Eric Tykwinski
TrueNet, Inc.
P: 610-429-8300
Joel:
Thanks so much for responding. As of now I can on run on-demand single processor scans.
Here are the things I would like to do:
- Run scans that utilize multiprocessors (I believe I do have clamd installed, I just don’t know how to use it)
- Schedule virus scans (a assume this can be done through a Bash script with Automator)
- Stipulate which volumes and directories to scan/exempt
- Choose to quarantine infected items
- Auto-scan files on access
There is probably more but that’s the lion’s share of what I’d like. Thanks for responding.
Happy New Year!
JS
What would you like to do other than what you have done? Seems like you were able to cover the basics.
Sent from my iPhone