Simon Hobson wrote: > > Today I've gone from having a server that "just runs" and has run with > virtually no oversight for several years to one that "just broke". > > I had to disable AV scanning this morning in order to get the mail > moving, now I've disabled freshclam and rolled back the database to > yesterdays version. > > Luckily it's not been a busy day today !
Personally, I keep my servers updated, so the EOL issue didn't affect me, but I agree with the others here. This was a bad idea. As others have mentioned not every sysadmin takes the time to follow the list or read the website on a regular basis. While it can be argued that they should have been doing this, I don't think it is fair to penalize them quite this severely. 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 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. 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. (Yes, I do realize that this would not help the old versions that are out there now, but if it is implemented in the next update, then it could be used when EOL for 0.96.1 rolls around.) -- Bowie _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
