OPER

Usage: OPER

Use /as oper to add or delete the network operators defined on your system. Options include access masks, flags or capabilities.

ACCESS - Change or modify Operators.

ADD - Add network Operators.

DEL - Delete current network Operators.

DISABLE - Disable the specified Operator profile.

ENABLE - Enable the specified Operator profile.

FLAG - Set the access permissions.

LIST - List the settings for a specific operator.

PASSWORD - Change an Operator password.

When oper is the only parameter used it will list all the opers currently configured on the server.

Example:

/as help oper <command>

Operators will have a great deal of power on the network and some users will trust them simply because of their operator status. Operators should always be chosen carefully. They should be familiar with your network's policies, trustworthy, and generally good at dealing with people. 
Ideally operators would all be familiar with the commands that run the network and how to fix most common problems, but the ability to learn and to find others to help when a problem is too difficult is more important than extensive chat knowledge.

Usage: OPER <name> ACCESS [<command>] [<mask>]

This will add hostmasks to your Operator definition. Hostmasks are used to prevent people from gaining operator status on your server from systems that you haven't defined. It is very important that you add proper masks to each operator definition.

ADD - Add a mask to an operator definition.

DEL - Remove a mask from an operator definition.

LIST - List all of the masks attached to an operator definition

Examples:

/as help oper access <topic>

An operator will only be able to gain access to operator privileges when matching one of the masks in the operator definition. It is important that all addresses that may be used are included in the operator definition. Requiring matching addresses is an additional level of security, although the password for the operator access should be the primary method of security. 
Always make sure that operators have secure passwords.

Usage: OPER <name> ACCESS ADD [<mask>]

You must use the form user@host, or user@IP - mark@*.conferencerooms.org, *@shell.org, *@127.0.0.1 are all valid where 10.25.12.10 and *.confrooms.org wouldn't be valid because they're missing the userid portion of the mask. You can use the * to replace segments of the hostname or IP address and you can also use a ? to replace a single letter or number in a hostmask. Like *@office??.conferencerooms.org.

Examples:

/as oper conferencerooms access add *@*.conferencerooms.org

The access mask is checked and if it doesn't match then even if you enter in the correct password the user will not be allowed to gain operator status.

Usage: OPER <name> ACCESS DEL [<mask>]

This command deletes a specified mask form the Operators access list.

Examples:

/as oper conferencerooms access del *@*.conferencerooms.org

The mask must match exactly to a mask that was placed using the OPER ACCESS ADD command. A wider mask will not delete masks that are contained in that mask.

Usage: OPER <name> ACCESS LIST

Lists the access masks that are configured for the Operator.

Example:

/as oper conferencerooms access list

Usage: OPER <name> ADD <password> <flags>

This will add a Server Operator To your server. It will only be available after you have added an access mask.

There are several different access levels. They are represented by single letter flags. In order they are:

Flag - Level

a - Server Administrator

c - Configuration Access

d - Disabled Operator

e - Require Encrypted

g - Global Operator

h - Helper

s - Services Administrator

Examples:

/as oper conferencerooms add mypa55 agcsh

Usage: OPER <name> DEL

This will remove the specified Server Operator

Examples:

/as oper conferencerooms del

Usage: OPER <name> DISABLE

This will disable the specified operator without removing any of their information.

Examples:

/as oper conferencerooms disable

Usage: OPER <name> ENABLE

This will enable the specified operator.

Examples:

/as oper conferencerooms enable

USAGE: OPER <name> FLAG [<command>] [<flags>]

There are several different access levels. They are represented by single letter flags. In order they are:

ADD - Adds the specified Flag

DEL - Deletes the specified Flag

LIST - Lists all Operator Flags.

Flag - Level

a - Server Administrator

c - Configuration Access

d - Disabled Operator

e - Require Encrypted

g - Global Operator

h - Helper

s - Services Administrator

If none of these flags are used the operator will be defined as a local operator. The h flag allows the person to see HelpOps and be marked as helpful. Giving someone the c flag gives access to the web based and online configurations. Configuration access should be reserved for only the most trusted personnel. 

Examples:

/as help oper flag <topic>

To see the abilities given to different flags see the OperServ and AdminServ sections of the Command Reference.

USAGE: OPER <name> FLAG [<ADD|DEL>] a

Services Administrator

USAGE: OPER <name> FLAG ADD [<flags>]

This will add the specified privilege flag to the designated Operator definition.

Examples:

/as oper celest flag add agh

To see the abilities given to different flags see the OperServ and AdminServ sections of the Command Reference.

USAGE: OPER <name> FLAG [<ADD|DEL>] c

Web Administration Configuration Access

This flag should be limited to those that can change the configuration of the server. It allows Operators access to the /as command set as well as the web based administration tools.

USAGE: OPER <name> FLAG [<ADD|DEL>] d

Disable the specified Operator

This allows you to disable the specified operator without having to delete all of their infomration.

USAGE: OPER <name> FLAG DEL [<flags>]

This command deletes the specified flag form the Operators list of privileges.

Examples:

/as oper celest flag del s

It's a good idea to limit configuration access only to those who really need it, use this command to delete all access flags from those Operators that don't need that level of access.

USAGE: OPER <name> FLAG [<ADD|DEL>] e

This makes sure that any user that wants to gain access to operator functionality must be using an SSL or secure connection.

A very good precaution to use when you have administrators and operators that are coming from remote ISPs where their passwords might be intercepted and then used to gain administrative access on your server.

USAGE: OPER <name> FLAG [<ADD|DEL>] g

Global Operator

This grants access to most of the normal services commands. This user can place klines, kill or disconnect users and get hidden user information. This also bypasses certain security blocks on the server.

USAGE: OPER <name> FLAG [<ADD|DEL>] h

Helper, or Helpop

This is a user that can receive helpops as sent by users when accessing the help system. Any time they send in a query that doesn't have a help topic a help notice with the query is sent out to all users that are +h.

USAGE: OPER <name> FLAG LIST

Lists all flags that are configured for the Operator.

Examples:

/as oper celest flag list

USAGE: OPER <name> FLAG [<ADD|DEL>] s

Server Administrator

Doesn't grant any additional powers but places a Server Administrator notice on a whois line.

Usage: OPER <name> LIST

This will list all the options of a specified Server Operator.

Examples:

/as oper conferencerooms list

Usage: OPER <name> PASSWORD <password>

This command will change an operator's password to whatever is sent in the last part of the command. Make sure you never give out passwords other than to their proper owners.

Example:

/as oper web password seqret4mula

Operator passwords should be changed immediately if they are ever revealed to anyone other than the person whose password it is. They should also be changed if the operator is having difficulty remembering the current one. A good password should be very difficult to guess, but not that difficult to remember so that it does not need to be written down.