[Pkg-clamav-devel] [Clamav-binary] [Clamav-mirrors] New ClamAV Package

[Joel Esler (jesler)]

David is absolutely right.  We are working on exactly that.

I don't know about your password issue... I can have someone look at that.

--
Joel Esler | Talos: Manager | jesler at cisco.com<mailto:jesler at cisco.com>






On Jan 31, 2018, at 2:42 PM, David Croft <david-clamavdb at infotrek.co.uk<mailto:david-clamavdb at infotrek.co.uk>> wrote:

On 29 January 2018 at 22:11, Heiko Richter <email at heikorichter.name<mailto:email at heikorichter.name>> wrote:

Furthermore at least one mirror admin that answered to the list has no
knowlege about the inner workings of a push replication system and is
completely ignorant of his server being broken. The "solution" of using cron
leads to dangerous states where clamav has no control over the mirrors
because those outdated and/or broken and/or dead mirrors that are
administered by incompetent people (sorry but thats how it is) present
security risks to all clamav users worldwide.

I don't think that's fair. He said it was put into place in addition
("supported by") when push mirroring not working.

I can empathise with this and give a current example. For two months
now we've been serving stale data. Our rsync password somehow works on
rsync2.clamav.net<http://rsync2.clamav.net> but not rsync1 (how this is even possible to not be
easily fixable is beyond me). The push script is directing us to sync
to rsync1, always, and is apparently not monitoring any errors from
the sync. Without a cron job syncing to rsync2 as a backup we'd still
be serving virus definitions from 29/11/17...

This whole process needs to be made more robust. Failure to sync
should notify at very least the local admin. The whole process should
be monitored out of band too by looking at the version files. Anything
that is not synced within a certain time frame should trigger
notifications and an automatic removal of the mirror until it is shown
to be consistently back in sync for a period.

Regards,

David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-clamav-devel/attachments/20180131/c48da28c/attachment.html>
-------------- next part --------------
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-binary
http://www.clamav.net/contact.html#ml