This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
All data has been migrated (including user logins/passwords) to a new phpBB version.
For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.
invite wrong ppl ??
-
cchefen
invite wrong ppl ??
hey i am using the latest netbots config and i have an +i channel. The bots nick was nick^ and the netbots invited a person who was called nick. The nick name is ofcourse not nick, any 1 has any clue why that was happening is it an bugg in netset or anything else.. Thought the bots checked the ident before it invite ppl or bots to the chan
It doesn't check on invite because it can't.
Eggdrop can only inspect security information that is available to it.
Netbots makes requests via the botnet. Whena bot sees it, it verifies the information provided.
Because the nickname isn't on the channel (why else would it be inviting it), it can't see the nickname to verify, so it invlites.
What you have discribed sounds like a flaw somwhere in the chain, though it doesn't confirm it is botnetop's at fault.
You may like to try botnetop.mod, which is a module version, and is compatable with the netbots component.
Eggdrop can only inspect security information that is available to it.
Netbots makes requests via the botnet. Whena bot sees it, it verifies the information provided.
Because the nickname isn't on the channel (why else would it be inviting it), it can't see the nickname to verify, so it invlites.
What you have discribed sounds like a flaw somwhere in the chain, though it doesn't confirm it is botnetop's at fault.
You may like to try botnetop.mod, which is a module version, and is compatable with the netbots component.
Under normal circumstances, the bot that is requesting the invite will tell the other bots over the botnet its current nick, and this will be correct. However, netsplits and/or lag could result in a bot inviting that nick when the requesting bot doesn't have it.
Whether botnetop.tcl checks a nick's host before inviting depends on the bop_icheck setting. Refer to the documentation for more information about it. This feature should greatly reduce the possibility of incorrect nicks being invited, but there are rare cases where it could occur (e.g. an inviting bot and an imposter with the same nick and host, with the real nick being on another side of a split, or lag between when the bot sends a WHO and receives a reply, and sends the INVITE, with the imposter jumping in somewhere in between).
Whether botnetop.tcl checks a nick's host before inviting depends on the bop_icheck setting. Refer to the documentation for more information about it. This feature should greatly reduce the possibility of incorrect nicks being invited, but there are rare cases where it could occur (e.g. an inviting bot and an imposter with the same nick and host, with the real nick being on another side of a split, or lag between when the bot sends a WHO and receives a reply, and sends the INVITE, with the imposter jumping in somewhere in between).