Is there any way to prevent aop's adding Hop or Vop?
They (Aops) can make anyone op although SECUREOPS is ON, by adding Hop or Vop. After that SECUREOPS doesn't exactly works, I mean, anyone that is not in Aop list, can be Op in channel.
How to Prevent Aop's adding Hop or Vop
Moderator: Supporters
Re: How to Prevent Aop's adding Hop or Vop
Yes. Don't make them AOPs .TECHNO wrote:Is there any way to prevent aop's adding Hop or Vop?
Or, switch on the numeric access list and set ACC-CHANGE above 5 (if using Anope).
Easy ways of managing ChanServ access lists. Found in IRCServices (and I think that Auspice had them too - and of course, there may be others that I don't know about).
There are four sets of related commands: SOP, AOP, HOP, and VOP. They're sometimes collectively referred to as teh XOP command set. (Indeed, to use these commands in IRCServices, you would load the chanserv/access-xop module.)
Here's a breakdown of what these commands are for:
If you want to read up further on this, the IRCServices manual would be a good place to start.
There are four sets of related commands: SOP, AOP, HOP, and VOP. They're sometimes collectively referred to as teh XOP command set. (Indeed, to use these commands in IRCServices, you would load the chanserv/access-xop module.)
Here's a breakdown of what these commands are for:
- SOP : auto +oa on channel join
- AOP: auto +o on channel join
- HOP: auto +h on channel join
- VOP: auto +v on channel join
If you want to read up further on this, the IRCServices manual would be a good place to start.