Hate to say it, but this is a stupid way to configure a virus scanner on a webserver. Tell it to exclude your mysql data directory. And in a production environment like this, it should probably be mailing someone a report rather than directly taking action on it. You're lucky it only got your bugs_activity table, seems the attachments table would be much more prone to this kind of thing.
After consulting with a few folks, we've decided there's not really anything we can do from Bugzilla to deal with this. There's a bug somewhere with an enhancement request to do virus scanning on uploads, but it would only deal with attachments, not comments. This is really a configuration issue with your virus scanner.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
I agree completely. I had already decided that this was a "DDT bug" (don't do that!) but figured it was well worth the waste of some ones-and-zeroes to pass this along. Thanks for the advice. I'm already going to speak with our server admin about preventing this situation in the future. Is there anywhere for this in future documentation though? Perhaps as a warning-block under configuration for either server or database? Thanks Dave!
You need to log in before you can comment on or make changes to this bug.