Scenario: Denying Operator Access To An Operator
Posted: Mon Feb 28, 2011 6:08 pm
Hello and good day to all. I've been working on creating my own private network for my friends, family etc. to connect to. As I am tackling this project seriously (and somewhat professionally) I'm trying to plan out various scenarios, and document what needs to be done. I've done some online searches via Google and on the forums but I haven't quite found what I am looking for. I'm not new to iRC but I am new to the whole administrative side of it (it's one of the reasons I started this project).
So here goes:
Here is an example of one of my operator definitions:
I have similar blocks set up for the network admin, services admin, server admin and server co-admin. My simple idea is to grant multiple iRC Operators access to a particular block. For example I may have 10 operators oper up using "/oper networkoperator networkoper". I have read many times on these forums:
Questions:
1. Is there a recommended method of defining operators in the oper block? What I mean is that, should there be a different oper block for every single operator on the network? Is there a standard way of defining iRC Operators?
2. Based on my oper block (all other opers, services admin, network admin etc. are defined as above) how would I go about removing her O:Line or disallow her from gaining access to this O:Line?
3. Short of actually adding an AKill or a GLine for her, what else can be done?
4. It has been said many times that you should just remove the O:Line for that user, but in the above example, doing so (removing the O:Line) would actually stop legitimate Operators. Is there something else that can be done?
Thanks in advance for any assistance or help with regards to this matter. I was going to put this in the Unreal Support forum, but on retrospect it didn't quite warrant "unreal support". So I placed it here.
MiRe
So here goes:
Here is an example of one of my operator definitions:
Code: Select all
oper networkoperator {
from {
userhost *@*;
};
password networkoper;
class clients;
flags {
helpop;
can_rehash;
can_wallops;
can_globops;
can_localroute;
can_globalroute;
can_localkill;
can_globalkill;
can_kline;
can_unkline;
can_localnotice;
can_globalnotice;
can_gkline;
};
};
Well here's my scenario: I get my network all set up, and I've given the O:Line described above to someone I trust, let's call her Melissa. Now some years pass, me and Melissa have a serious falling out, say, she doesn't like how the network is being administered, and she ends up being disruptive to the network. Let's also say that some other operators support her cause, and notify her of: when I change the password; or when I change the host in the from section.aquanight wrote:If you don't trust your opers, don't make them opers.
Questions:
1. Is there a recommended method of defining operators in the oper block? What I mean is that, should there be a different oper block for every single operator on the network? Is there a standard way of defining iRC Operators?
2. Based on my oper block (all other opers, services admin, network admin etc. are defined as above) how would I go about removing her O:Line or disallow her from gaining access to this O:Line?
3. Short of actually adding an AKill or a GLine for her, what else can be done?
4. It has been said many times that you should just remove the O:Line for that user, but in the above example, doing so (removing the O:Line) would actually stop legitimate Operators. Is there something else that can be done?
Thanks in advance for any assistance or help with regards to this matter. I was going to put this in the Unreal Support forum, but on retrospect it didn't quite warrant "unreal support". So I placed it here.
MiRe