>> Most recent update from them was 3 months ago. > > rsync rsync://rsync.mirror.msrbl.com/msrbl/MSRBL-SPAM.ndb > -rw-r--r-- 244643 2009/07/27 01:21:23 MSRBL-SPAM.ndb > > rsync rsync://rsync.mirror.msrbl.com/msrbl/MSRBL-Images.hdb > -rw-r--r-- 181337 2009/07/24 03:40:17 MSRBL-Images.hdb
rsync rsync://rsync.mirror.msrbl.com/msrbl/MSRBL-Images-FULL-SoN.hdb -rw-r--r-- 19030813 2009/10/07 15:50:05 MSRBL-Images-FULL-SoN.hdb 3 months ago. >>> Only your orphaned botnet project. >> >> Still not orphaned, still not in need of a new version, and you're >> still not qualified to make that declaration. > > Strange that others must provide patches for your project them, since > you haven't provided an update in nearly 3 years. Only a very few sites seem to need it, making it, as far as I've observed, an edge condition. Not a general need. There hasn't been any OTHER reason to make changes to it. If there was something critical and wide-spread, sure. If there was a new feature to incorporate, sure. Neither of those are true. And, as I've said before, and you're well aware, the direction that the given patch goes isn't the direction I want to go with botnet. The change doesn't need to be in the general dist. The change doesn't fit the direction I want to go with the package. There aren't any other reasons to update it. So there hasn't been a need to update it in 3 years. That doesn't make it orphaned. It makes it "not in need of new releases". If one of those needs comes up, if the plugin API changes, or if I see the need for a new feature, it will get addressed. All of which gets back to: you have no business making announcements about projects for which you aren't a spokesperson. So, when you do make those announcements, it's perfectly reasonable for someone to ask you back up your statement ... because your statements lack credibility. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
