Eric Rostetter wrote: > Quoting Bowie Bailey <bowie_bai...@buc.com>: > >> A suggestion for the future... Rather than disabling clamd with the EOL >> signature, have freshclam key on the signature (or something else about >> the file) and fail the update with a notice that the current version is >> no longer supported. > > This won't work unless we can predict all future needs... How could > they have predicted the kill-signature 5 years ago, to include in the > old code?
Obviously this is not a retroactive solution, but now that they know this may be necessary, something can be changed so that it can be dealt with more smoothly in the future. >> This way the server will continue to run with the >> old signatures, but there will be a notice in the logs that there is a >> problem. > > You assume they will check the log... And if they do, that they will > take some action. Both are bad assumptions. Probably better than assuming that everyone will check the website or mailing list. At least no one could claim the information wasn't easily available if it was right there in their own server logs. >> More generally, maybe there should be a capability in >> freshclam for messages to be sent from the developers. Freshclam could >> look for a message whenever it does an update and if it sees one, it >> could print it in the logs. This would give an easy way to notify users >> of upcoming changes or other important issues. > > Interesting idea... But it only works if you can get everyone to upgrade > to the new version that supports this. How do you do that? As we've > seen, > by killing their old versions... So the killing still can't be > avoided... All you can do is make improvements in the current code. Short of inventing a time machine, there's not much that can be done about deficiencies in older versions. -- Bowie _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
