> >> I don't know of any way to stop freshclam from updating.
> >> Some mirrors can blacklist old versions, but not most/all.
> >
> > Using a new DNS tree, such that old freshclam versions were unable to
> > perform the job?
>
> The DNS servers don't receive any information about the version of
> freshclam used to perform the query.
> The DNS request can go through many DNS caches...
So what?
I see the old freshclam issues DNS request like these:
current.cvd.clamav.net.
What if this DNS name stops responding (and be propagated to mirrors) and
instead a new current1.cvd.clamav.net (or maybe current.cvd1.clamav.net if
you dislike the first) start working? Clamav's 0.96 could issue requests to
that brand new name to get updates, while old clamav installations -which
are unaware of it- would simply fail updating.
They would probably scream error messages in big letters in their logs, but
their clamscan would keep running...
Please also note that the fact that "[clamscan will stop working] was
clearly stated" (if any) may have a meaning in a lawsuit. But it is not an
excuse (in the world of the open software) if any other way to have a
forward- and backward-compatible solution is available...
I personally I'm sure I'm not going to file a lawsuit against anybody, since
I have cutes 0.96 up and running in the servers I directly manage. Nor I'm
going to switch, also because I often have more than one AV running in my
mail servers.
Nevertheless, a *lot* of people will abandon clamav in favor of some
pay-per-clean solution (which may even not be a 3D System, after all).
Was this the purpose?
Giampaolo
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
