Follow me on twitter

Ticket #45 (closed enhancement: fixed)

Opened 5 years ago

Last modified 6 months ago

config option to run an entire botnet in umode +g

Reported by: sknake Owned by: bryan
Priority: minor Milestone: 1.3
Component: irc Version: 1.2.2
Keywords: Cc:

Description

i want the ability (such as .config umodeg 1) so i can run an entire botnet in +g mode. the reason for this is when people packet bots and they can only lag the shit out of them but they're still responding they'll mass msg the bots and the server will only allow you to queue up X amount of data.. when too much is pending then it /kills <client> (Max SendQ Exceeded) .. so by running an entire botnet in +g it will eliminate this and make the bots stay on longer. How i suggest msg commands work is that when a message comes through you match the host of the user and if its a user do: issue the raw command ACCEPT <nick>,<nick>,<nick>,... and when it fills up remove the oldest nick.. so you can /msg <bot> fuckoff <bot> /raw ACCEPT $ACCEPT,$NICK /msg <bot> op

just one more message for a little more protection and it'll confuse the hell out of people having a botnet in +g

:)

as stated in modeg.txt when a user changes their nick they're removed from the /accept list so you cant track them.

If the bot picks up on a nick change of a +n user already in the accept list i'd like the bot to go ahead and track it. +o's will get ops and wont message the bot again until they reconnect but i'm always changing nicks and using the net.

ok i played around with this some more and i noticed the max for umode g (on blackened) is 20 users and this was the same on a few other servers.

also when you set mode -g it keeps your accept list. this probably wont come in to play but i noticed it.

Attachments

modeg.txt Download (5.4 KB) - added by sknake 5 years ago.

Change History

Changed 5 years ago by sknake

Changed 5 years ago by bryan

If +g system is on, don't bother with accept lists with -c bots.

Changed 10 months ago by bryan

  • type changed from defect to enhancement

Changed 6 months ago by bryan

  • milestone set to 1.2.17

Must expire nicks after a while to prevent maxing out the list. As stated above, only +c bots will even consider adding a user to the list.

This will also break msg-ident, but it's insecure anyhow.

Changed 6 months ago by Bryan Drewery

  • status changed from new to closed
  • resolution set to fixed

* Add set 'callerid' to run bot in CALLERID mode (+g). +c bots will automatically accept messages from known users. (fixes #45)

Changeset: 5966564b06119ab465466c97e7f3844809522503

Changed 6 months ago by Bryan Drewery

* Automatically accept messages from users when in CALLERID mode (fixes #45)

Changeset: 082537ae707fc5006e31867d27601b2097be74a7

Changed 6 months ago by Bryan Drewery

* Add set 'callerid' to run bot in CALLERID mode (+g). +c bots will automatically accept messages from known users. (fixes #45)

Changeset: 5966564b06119ab465466c97e7f3844809522503

Changed 6 months ago by Bryan Drewery

* Automatically accept messages from users when in CALLERID mode (fixes #45)

Changeset: 082537ae707fc5006e31867d27601b2097be74a7

Changed 6 months ago by Bryan Drewery

Merge branch 'deaf-and-callerid'

* deaf-and-callerid:

  • Assuming CALLERID=g and DEAF=D if the IRCD does not provide the flags
  • Fix sort of variables. flood-callerid was out of order.
  • Fix grammar error
  • Automatically accept messages from users when in CALLERID mode (fixes #45)
  • Rename set 'flood-g' to 'flood-callerid', which only takes affect if the server supports CALLERID.
  • Add set 'callerid' to run bot in CALLERID mode (+g). +c bots will automatically accept messages from known users. (fixes #45)
  • Set DEAF mode when appropriate.
  • Reset rare IRCD features back to default when disconnecting from server
  • Detect if DEAF is supported, and what character to use
  • Add set 'deaf' to run bot in DEAF mode on supporting IRCDs. This prevents channel conversations coming to the bot. On by default.

Changeset: f65c1ce3b065f21b9ff81bba53339fa3587fa3e1

Note: See TracTickets for help on using tickets.