Helpop flag -> Local Operator flag

igarvey · Post by **igarvey** » Sat Dec 17, 2005 3:17 pm

Why does the helpop flag assume the local operator flag? For instance, if you make an operblock wherein the only flag designated is "helpop", that user will be given local operator status on oper-up:

For instance, if I set up the following oper block:

Code: Select all

oper igarvey-helpop-test {
        class clients;
        from {
                userhost *@*;
        };
        password "$SDjuQNQj$tLsZnN3j4HTi6N4tKzqyelLvM2M=" { sha1; };
        flags {
                helpop;
        };
        snomask fkejGqsSo;
        swhois "is a help operator";
};

Upon opering up, that user gets:

* igarvey-helpop-test sets mode: +wghsOv
Server notice mask (+kfjeGqSso)
You are now an IRC Operator

(Local IRC Operator!)

However, that user cannot /kill or /kline anything. For some reason it is given the locop flag on default -- but it's a completely deprecated local operator that can't do anything except things like /stats G and receive snomasks. (Though it has the * is a Local IRC Operator in whois) Why is this?

JIVXor · Post by **JIVXor** » Sat Dec 17, 2005 4:39 pm

HelpOperators are ircops too and thats the purpose "TO HELP" not to do "/stats g" or "/kline +@bla" .

By the way, you can put the snomasks to him/her that you want, I think it is not a necessary and sufficient condition to be a local operator to use the snomasks.

igarvey · Post by **igarvey** » Sat Dec 17, 2005 5:42 pm

JIVXor wrote:HelpOperators are ircops too and thats the purpose "TO HELP" not to do "/stats g" or "/kline +@bla" .

By the way, you can put the snomasks to him/her that you want, I think it is not a necessary and sufficient condition to be a local operator to use the snomasks.

If they do not have /kline, /kill, or any other such capacities that come with being a locop, why are they called "Local IRC Operators" once opering up and in /whois? They clearly don't have that status.

JIVXor · Post by **JIVXor** » Sat Dec 17, 2005 5:57 pm

Yes, they have that status 'cause they are Local Irc Help Operators, the intention of a local operator is not nothing else that to put line to an IP, to do a /rehash, to do a /stats G, etc etc. You can be an operator and the only privilege that you have is the one to add lines to unrealircd.conf, nevertheless you cannot do a /kline +@bla, you cannot do a /samode bla. The only function that you have is to :

/addline bla bla bla
/rehash

It is truth that is a little strange to be a local operator that nothing else it does that, but is necessary to divide the work. In my opinion I believe that is not so annoying to create a block for helpops.

It is annoying for you ? Or you are not only in agreement with the concept of "Local IRC Operators" ?

I understand you after all. That also happens to me.

aquanight · Post by **aquanight** » Sat Dec 17, 2005 9:51 pm

If you have any oper block at all, then upon using it you will at least get either usermode +O or +o - you can't get just +h for example. The nice thing is you can then ask for all ircop privs to be dropped with /mode nick -O and not have to handle special cases like /mode -h when they have or don't have +o or +O. Furthermore, the line in /whois is decided by the presence of +o or +O usermodes, not the oper block setup (read the m_whois.c code if you want to see what I mean).

Generally, if you have an oper block, you are an IRCop, even if you are limited to just helpop. On that note, there are a few things that all IRCops get regardless of flags (eg: access to modes +g, +W, all /set* commands, and (generally) all snomasks, also global opers always get immunity to command throttling, local opers can get it depending on a #define switch).

(The nice thing about having just helpop means you can give the oper a limited subset of what local opers normally get automatically, eg, kill/kline/etc.)