Chanops Nick Abuse

simo · Post by **simo** » Tue Mar 28, 2023 7:27 pm

greetz folks,

i was trying out this small code to check for nicks joining channel and nick changes to check if joining nick or nick change has chanops nick in it and i was wondering if this is the best way to do it or is there another way not to have to loop each time a nick joins or changes nick ?

here is what we work with :

Code: Select all


bind nick - * Chanops-Nick-Abuse

proc Chanops-Nick-Abuse {nick uhost hand chan newnick} {
    Chanops-Join-Abuse $newnick $uhost $hand $chan
}




bind join - * Chanops-Join-Abuse

proc Chanops-Join-Abuse {nick uhost hand chan} {
   if {[isbotnick $nick]} return
   set userList [chanlist $chan]
   foreach user  $userList {
      if {[isop $user $chan] || [ishalfop $user $chan] } {
         set length [string length $user]
         set bdnickpart [wildcard $user]
         regsub -all {\*{1,}} $bdnickpart "*" bdnickpart
         if {[string match -nocase "$bdnickpart" $nick] && $length > 5} {
            pushmode $chan +b *$user?*!*@*
            pushmode $chan +b *?$user*!*@*
            regsub -all -- ~ $uhost "" uhost
            if {[string match -nocase "*@*irccloud*" [maskhost $nick!$uhost 2]]} {
               set ident  "[lindex [split $uhost @] 0]"
               set xbmaskx "[string map {sid id uid id} $ident]"
               set bmask  "*[string tolower $xbmaskx ]@*"
               pushmode $chan +b $bmask
            } else {
               set bmask "[maskhost $nick!$uhost 2]"   
               pushmode $chan +b $bmask
            }
            putquick "kick $chan $nick « -- Please Dont Impersonate/Abuse Chanop Nicks Thank You.... -- »"
            break
         }
      }
      flushmode $chan
   }
}
 
proc wildcard {text} {
   set sep {*}
   set reg $sep
   for {set i 0} {$i<=[string length $text]} {incr i} {
      append reg [string index $text $i]$sep
   }
   return $reg
}

the chanops nicks we check using xbn2regx process as some try to hide chanops nicks in an abbussive nick like:

c_hano|-ps

and such

simo · Post by **simo** » Fri Mar 31, 2023 12:35 am

Basically what I lm asking is will the constant loop through chanlist to find chanops to compare to the joining nick have bad effect on performance and if so is there a better way to achieve the same result without loss of performance?

Post by **caesar** » Fri Mar 31, 2023 11:11 am

Those two binds (nick and join) should be more than enough to cover your needs, without the loop over chanlist every time someone joins. Makes no sense really.

Not to mention the code is poorly formatted.. here's a better look to follow things more easily.

Code: Select all

proc Xchanop:nick-checkerX {nick uhost hand chan} {
	if {[isbotnick $nick]} return
	set userList [chanlist $chan]
	foreach user  $userList {
		if {[isop $user $chan] || [ishalfop $user $chan] } {
			set length [string length $user]
			set bdnickpart [xbn2regx $user]
			regsub -all {\*{1,}} $bdnickpart "*" bdnickpart
			if {[string match -nocase "$bdnickpart" $nick] && $length > 5} {
				pushmode $chan +b $user?*!*@*
				pushmode $chan +b *?$user!*@*
				regsub -all -- ~ $uhost "" uhost
				if {[string match -nocase "*@*irccloud*" [maskhost $nick!$uhost 2]]} {
					set ident  "[lindex [split $uhost @] 0]"
					set xbmaskx "[string map {sid id uid id} $ident]"
					set bmask  "*[string tolower $xbmaskx ]@*"
					pushmode $chan +b $bmask
				} else {
					set bmask "[maskhost $nick!$uhost 2]"
					pushmode $chan +b $bmask
				}
				putquick "kick $chan $nick «--dont-do-that--»"
			}
		}
		flushmode $chan
	}
}

As it stands right now only the op and halfop are checked when a user joins the channel.

Post by **CrazyCat** » Fri Mar 31, 2023 12:19 pm

And why not use:

Code: Select all

set userList [chanlist $chan +o|+h]

chanlist can filter on flags

simo · Post by **simo** » Fri Mar 31, 2023 12:58 pm

Thanks for the reply CC and caesar

Caesar: the reason i have to loop throu chanlist to find chanops halfops on each joining nick is because its ops and halfops nicks that get abused who are currently opped and i dont use flags as their IP is dynamic so i cant rely on that

In reaction to your question crazycat is because we wanted to check the actual nicks with a @ or % in the channel

simo · Post by **simo** » Fri Mar 31, 2023 6:06 pm

Caesar :

Those two binds (nick and join) should be more than enough to cover your needs, without the loop over chanlist every time someone joins. Makes no sense really.

how else are we suppose to get the current chanops/halfops in the channel on every join ?

Post by **caesar** » Sat Apr 01, 2023 2:29 am

On a bind mode change? I fail to understand what exactly is happening there and what exactly you want to achieve.

simo · Post by **simo** » Sat Apr 01, 2023 3:56 am

caesar wrote:On a bind mode change? I fail to understand what exactly is happening there and what exactly you want to achieve.

First a bind mode change is not what i used i used a bind join and a bind nick as it's the nicks we want to compare

What we want to achieve is everytime a nick joins or changes nick we want to check it if it has the nick of a chanop/halfop in it (who is currently in the channel and half/opped) wich is mostly used for abuse and if detected to set ban on the abuser and set ban on chanop nick that got abused without getting the actual chanhalf/op banned

Post by **CrazyCat** » Sat Apr 01, 2023 6:31 pm

And what happens with ghost (often on timeout ?)
Usually the client reconnects with an alternative nick, often a variation of the main nick, while the main is still connected.

You'll ban nick- because it looks like nick ? And nick- is the real op, nick is just a ghost which will disappear in a few seconds.

simo · Post by **simo** » Sat Apr 01, 2023 7:22 pm

Thats a good point crazycat i didn't find that the case with most chanops but it may happen once in a long time and if it happens a lot there is something else going on that needs fixing

Post by **CrazyCat** » Mon Apr 03, 2023 10:06 am

simo wrote:In reaction to your question crazycat is because we wanted to check the actual nicks with a @ or % in the channel

Read the documentation and the line I put:

Code: Select all

set userList [chanlist $chan +o|+h]

This will restrict the userlist to @ and % users only, that's the same as caesar did, but potentially faster and using less memory.

Post by **caesar** » Mon Apr 03, 2023 10:59 am

I didn't do anything, just made his code easier to follow by adding indentations.

I would maintain an active list of the names I want to "protect" via mode change, quit, part, and so on, and upon a regular user joining I would check with that list. I doubt you have 100 names to keep track at any given time, so this approach would be far less memory intensive than looping the entire channel members list for every single trigger by a bind join.

simo · Post by **simo** » Mon Apr 03, 2023 1:33 pm

That would be ideal CrazyCat except some of the chanops dont use a fixed Host
so we dont have anything fixed to use auth them

Post by **CrazyCat** » Mon Apr 03, 2023 6:35 pm

@caesar : I just said that using the flag filter in chanlist is the same as doing

Code: Select all

set userList [chanlist $chan]
foreach user  $userList {
   if {[isop $user $chan] || [ishalfop $user $chan] } { ... }
}

We just don't filter @ same time

@simo : where the f*ck did I speak about auth ? I was just giving a way to use a reduced userlist. I didn't try to solve your potential ghost trouble.

simo · Post by **simo** » Mon Apr 03, 2023 11:20 pm

Oh ok i guess I misunderstood as i though in the example gave with:.

Code: Select all

set userList [chanlist $chan +o|+h]

I though the +o|+h was flags my mistake

I'll test some more using that.

Thanks,