Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Master]

Well, it was set up before that IRCops were immune to being akicked or banned via ChanServ...which helped IRCops do their jobs when it came to affairs that come up often. However, the admin had to restart services from the ground because of a shell breach, and now all IRCops, including those who are services roots, are affected by these (even with +q set, although that doesn't matter anyway). Is there a config option that was overlooked?

[Jan Milants]

IRCops are there to administrate the serves.. they have no business in overriding channel settings imo, hence why to chanserv akick they are just regular users. Should they need to get involved in a channel they can use superadmin which grants them the same rights as the channels' founder.

You might wanna take a look at http://modules.anope.org/viewmod.php?id=79
But i for one have no interest in being on a net where ircops (think they) are gods...

[Master]

Well, the whole purpose of it was to protect IRCops from being banned should a user attempt a channel takeover (i.e, banning *@*). It happens quite frequently...

[katsklaw]

There is a huge difference between banning *@* and akicking *@*. Services can do jack squat about banning *@* because it's 100% controlled by the ircd. If you use Unreal, there is also umode +q and a module on the modules site that stops services banning services opers and above, Viper provided the link. Also with Unreal there are more commands for overriding stuff than you can shake a stick at.


Perhaps you should invest some time in the /os help chankill command. It allows you to remedy the issue without even going into channel in the first place.