If I were in your position I'd also use rsync as that is what I did when I was
in your position (retirement is a fine thing). It also provides a very
atomic-like operation so if clamd or clamscan needed to read the signatures
they're not in a half-there state. Your case involves protecting intellectual
property and that is justification for just about any solution you can come up with.
dp
On 12/29/14 6:43 AM, Torge Husfeldt wrote:
Hi,
Am 24.12.2014 um 12:09 schrieb Arnaud Jacques / SecuriteInfo.com:
Le mardi 23 décembre 2014, 10:56:37 Dennis Peterson a écrit :
Second try:
What problem are you trying to solve with https?
Privacy.
I'd like to expand upon this.
For the standard use-case using the official sources this might be
irrelevant and actually present more draw-backs than advantages.
But: just like the original poster we have a DB of "internal" signatures
and we had to solve the exact same problem.
We resolved not to use freshclam at all but rsync/sigUSR1 the updated
signatures to our ~20k Servers.
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
