Oper block

In oper blocks you define all the IRC Operators accounts. Once defined you use the /OPER command on IRC to become IRCOp.

Syntax
oper { /* Required items: */ mask ; password ; class ; operclass ; /* Optional items to further limit who can /OPER */ require-modes maxlogins ; /* Optional items to define what will be set upon successful /OPER */ swhois ; modes ; snomask ; };

name
The name in the oper name { block defines which name to use in the OPER command on IRC (/OPER name password). This name is case sensitive!

password
The password item defines the password to use. Passwords are case sensitive. Instead of using a plaintext password here, we highly recommend you to use Hashed passwords or SSL certificate fingerprints, see Authentication types.

mask
The mask defines from which host/IP this oper block may be used, this can be used for increased security. Set this to mask *; if you want to permit any IP. You may also use multiple masks, in which case the syntax becomes like: mask { 1.2.3.*; 55.66.*; 11.22.*; *.co.uk; };

class
After a successful /OPER attempt the user will be put in the class you specify here. This can be the same as any other clients (eg: class clients;) or some special class you created for IRCOps (eg: class ircops;)

operclass
operclass defines which Operclass block. The operclass defines which privileges this IRCOp will have (which IRCOp commands you may use, etc..).

require-modes
This lets one specify modes (such as 'z') that a user must have acquired before being allowed to OPER. This can be used, for example, to require opers to be on secure connections (user mode +z) before being able to become operators.

maxlogins
This allows you to restrict the number of concurrent oper logins from this host, for example if you set it to 1 then only 1 person can be oper'ed via this block at any time.

swhois
Allows you to add an extra line to the /WHOIS information for this oper. For example: swhois "a Network Administrator";

modes
Set these user modes after successful oper up.

snomask
By default an IRCOp gets the Snomasks from set::snomask-on-oper. You can use this oper::snomask to specify a different set of snomasks. See Snomasks for a full list.

Example
oper bobsmith { class clients; mask { smithco.com; *.somedialupisp.com; }; password "f00"; operclass netadmin; swhois "a Network Administrator"; snomask cFfkoSsqNG; };

Some little information about OperOverride
OperOverride are things like: joining a +ikl channel and going through bans, op'ing yourself in a channel, etc. See the OperOverride article for all information on this.