-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 ilias seperis wrote:
> The thing is that there is no point using proxy on > "headquarters linux server" because the "remote linux > server" doesn't use tcp/ip to communicate with the > "headquarter linux server". In fact the "remote linux > server" uses typical dialup, and receives/sends data > with uucp with no tcp/ip due to the overhead. > So let me describe once more the scenario (hopefully > more accurate): > > (internet) -> headquarters linux server -> satellite > communication (very expensive, slow, unstable and no > tcp/ip at all) -> [[ remote linux server -> (lan) -> > windows clients ]] > > The .cdiff files u mentioned might just do the trick. > The questions however are: > 1) which .cdiff files do I download? I don't know how the new protocol works. Using the DNS query freshclam notices a new version of the DB is available, then asks for all the update script files. An option would be using 'sigtool --diff= old.cvd new.cvd', but I'm not sure if this diff is the same as the scripted updates. This thread has moved into the "need an expert" area, and the question is: how to set up a private mirror? > 2) Assuming that these cdiff files are transfered to > the "remote linux server", how do I feed the > freshclamav of the "remote linux server" with these > files? You don't, in this case you would use 'sigtool --run-cdiff=...' > 3) The same question goes with the rest of the > "windows client". How they will be updated? If you want to keep the clients as they are, then you need to handle their DNS query and configure them to use your server as their mirror. That looks like the easy part. - -- René Berber -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Cygwin) iD8DBQFHB2FtL3NNweKTRgwRCAqEAKCd3bS/Gjbdi4E8mf5d1089vgiYnQCfZqR9 G268aWGTcaMYF/+gu/gbJGE= =v0Kj -----END PGP SIGNATURE----- _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
