Raja Muhammad Hammad said: > does ClamAV support the given scenario? ClamAV is neutral on the subject. It provides only the freshclam tool but no server - it really doesn't care where that server is. There are several ways to accomplish what you want:
* If a server is visible to all systems on any particular port you choose then you can make that a central server for all systems and avoid delays in relaying from one to the next. * If relaying is necessary then you simply set up some file transfer method and schedular. Among your options for both Linux and Windows: ftp, http, scp, rsync. Any of these methods can be used for a truely central servers as well. If you use httpd for a server method then freshclam can be run on any client where it's needed. You can also use wget or curl as a client. scp requires sshd run on at least one system - scp is the client. Ftp should require no explanation. Rsync also requires a server run on at least one system - the central site, perhaps. Your architecture will depend upon whether you pull the files from the collector system or push them to the clients. Finally, and least secure, you can share the files using NFS and Samba. An NFS client is available from Microsoft, and NFS ans Samba are already in Linux. Ignoring for the moment that the need to to share ClamAV files, any file shareing method that is common to all the systems, and for which minimal automation can be scripted, will work. Even in Windows. Personally, I use rsync as it transfers data only if necessary and is rather secure. dp _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
