Ok, first of all I would like to say that I know credit should be given where credit is due. Also that mIRC is a wonderful IRC client and in my opinion the best client for Windows.
But unfortunately the inability disable or atleast put a timer on the version reply has been used to leverage drone attacks on IRC networks and their users....
So my suggestion is in the next version of mIRC, add an anti-flood option specifically for the version reply that works on a timed basis. Maybe only allow it to send one version reply every 30 seconds or something... The way it is now, drones can have a field day with it. The flood protection for CTCP's just isn't enough.
If someone has a working solution to this problem already, please reply and let me know.
I see the 10 second timer, but the problem is that its per user. I am talking about drone nets in 1000's in size, and they like to change their nicknames about every 15 seconds or so. A 10 second wait PER USER is not enough. If anything it should be just 10 seconds between each version reply altogether.
Well, I didnt really time it exaclty. But regardless of what it is, the problem still exists that attackers can abuse this due to version being hardcoded into mIRC, if it wasn't hardcoded like all other CTCPs that can be modified via scripting, I would be able to make my own timer and it would solve this problem. I had to ignore all CTCP last night in order to stay on Undernet because of this.
OK, well if that is the case, it would still be nice to have better control over how often it will reply. Even with it at 10 seconds it was still causing me problems with changing targets too fast error on Undernet and my regular script I run. Is there a way to make it more than 10 seconds?
Yea, thats a nice temporary solution. But the problem is I do need some CTCPs. A script I use actually expects to get channel CTCPs. So turning CTCP off completely wouldnt be a great permanent solution for me.