Török Edwin wrote: > Would you prefer freshclam/ClamAV crash/corrupt memory when loading the > new databases with >980 byte lines?
No. I can think of ways around this to make things degrade gracefully: o The server could look at the Freshclam user-agent version number and not serve up the new database if it's too old. o The 0.96 Freshclam client could use a different request to get the newer longer-lined files. (I guess it's a bit late for that now...) > The initial announcement about this was 6 month ago. > If a 6 month window to upgrade is not enough, what would be? Nothing justifies a kill-switch. You seem quite naive regarding real-world customers. Many of our customers are not very computer-savvy. They can sometimes be hard to reach. And some of them have insanely bureaucratic rules about how and when software can be upgraded... we still have people who insist on running Red Hat Enterprise Linux 4 because they don't want to change. I understand your frustration with people who take a long time to upgrade. But a kill switch to force the issue is most unwelcome. It also implies that anyone who somehow gets hold of your signing key can kill every ClamAV installation throughout the world. :( Regards, David. _______________________________________________ http://lurker.clamav.net/list/clamav-devel.html Please submit your patches to our Bugzilla: http://bugs.clamav.net
