hi, > Tcpwrappers hearkens back to a time before firewalls.
true. but, even clamav makes it available as a build option (fairly recently added, iirc?) -- just for clamav-milter, NOT clamd ... but you're correct. > But why is your second option not optimal? Simply 'one more thing' to take care of ... external to the apps involved. > clamd.conf is where you should tell clamd where > to provide it's service. Likewise, the OS firewall is the place where you > should tell your OS who can access your services. if that were uniformly true, that would be great ... but, per my example, SA & Exim take a different approach, allowing that specification WITHIN the app's config space. > For example, if you're running RHEL using a firewall (in my case, pf (freebsd/openbsd) or ipfw (osx), not that it matters ...) it's certainly clear. just looking to see if/how its doable from 'within' clamav's clamd. thanks! _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
