After applying the long name patch to the bot, it will cease to function with eggdrops that are not patched as the handle lengths are no longer matching. This ebuild should probably be masked so that people don't break their botnets with the upgrade. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I somehow knew that this would come up. It was added by an user request in bug #66390.
*** Bug 86580 has been marked as a duplicate of this bug. ***
I know it was added by user request, but it still causes the bot to be incompatible with any other eggdrop but 1.6.17-r1. For users with a single bot on a random ircd that supports nicks longer then 9 characters, teh patch is great, but for people with large botnets on "major" irc networks (of which most support only 9 chars and a couple support 10) this patch is not only useless, it breaks the botnet. Should either be removed from the portage tree (it's not hard to create a local ebuild for patches of this nature) or masked (but that's not appropriate as there will be continuing problems as version progress) or be attributed to a USE flag (which would be considered cruft by most).
The patch modifies the maximum length of the internal user handle. The handle has nothing to with the nick used by users on IRC. They're totally unrelated. That it breaks botnet linking is correct.
In that case the point of the patch is even less apparent...
Well, it allows you to give your users more descriptive handles. By default eggdrop supports IRC nicks up to 32 characters, but only 9 characters for handles, so if you're on a network that supports >9 characters for nicks and your users use such long nicks you have to shorten them for the handles making IRC nicks <-> handles mapping much harder for yourself.
That has nothing to do with the fact that this patch breaks existing user databases. This version (and all in the future that contain this patch) have to be masked for those that don't want/can't update their countless eggdrops on the botnet.
net-irc/eggdrop-1.6.17-r2 in CVS.
