James Lu 580ca7498c Namegen/NoTrigger: more PEP8 things
Again skipping the config.py things (for now).
2014-12-27 11:46:44 -08:00
..
2014-09-20 17:27:27 -07:00
2014-12-27 11:46:44 -08:00
2014-12-27 11:46:44 -08:00
2014-12-27 11:46:44 -08:00

NoTrigger is an anti-abuse script that modifies outFilter to prevent triggering other bots.

Short description

In short, NoTrigger works by:

  • Prepending messages that start with a symbol (!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~) with a space, since these are often used as prefixes for bots.
  • Prepending messages with a space if the channel is set to block colors and a message begins with a formatting code (sneaky attackers can otherwise do something like \x02!echo hello to bypass filters).
  • Optionally, prepending messages with a space if they match <something>: or <something>, , since some bots are thought to respond to their nicks.
  • Optionally, blocking all channel-wide CTCPs (except for ACTION).

Longer description/Backstory on why I made this

Sometimes if you have a public development channel with many bots residing in it, someone will come along and do something really evil: that is, create a huge message loop by chaining all your innocent bots together!

For example:

<evilperson> !echo @echo $echo &echo abcdefg
<bot1> @echo $echo &echo abcdefg
<bot2> $echo &echo abcdefg
<bot3> &echo abcdefg
...

NoTrigger aims to solve some of these issues by prepending messages that start with commonly-used bot triggers with a space. For example:

<evilperson> !echo @echo $echo &echo abcdefg
<securedbot>  @echo $echo &echo abcdefg
...

Boom. Problem solved, right? Well, almost.

Some bots will also respond to their nick!

<evilperson> !echo bot2: echo bot3: echo i lost the game!
<bot1> bot2: echo bot3: echo i lost the game!
<bot2> bot3: echo i lost the game!
...

This is slightly harder to parse, so we have to check if a message matches <something>: <text> or <something>, <text> (where <something> can be used as the name of a bot).

OKAY OKAY, now our bot is really foolproof, right?

ALMOST! Then there are the truly evil ops (shoutout to @jacob1) that start messing with your bot by introducing colour stripping! :D

Fortunately, we'll append these message with a space too! (when the channel is set to strip colours, of course.)

Before:
Channel is set +c.
<evilperson> !bold "bot2: echo bot3: echo i lost the game!"
<unsecuredbot> bot2: echo bot3: echo i lost the game!
<bot2> bot3: echo i lost the game!
...
After:
Channel is set +c.
<evilperson> !bold "bot2: echo bot3: echo i lost the game!"
<securedbot>  bot2: echo bot3: echo i lost the game!

That's all! Find any more ways to abuse a poor, innocent bot? Let me know on the issue tracker! 😝