Example configuration for opertypes and oper blocks, initial version written by DukePyrolator with a little refinement and addition by me.

git-svn-id: http://anope.svn.sourceforge.net/svnroot/anope/trunk@2348 5417fbe8-f217-4b02-8779-1006273d7864

1 files changed, 106 insertions, 0 deletions

diff --git a/data/example.conf b/data/example.conf
index 249b79334..830f518c9 100644
--- a/data/example.conf
+++ b/data/example.conf
@@ -491,6 +491,112 @@ options
 	ulineservers = "stats.your.network proxy.your.network"
 }
 
+
+/*
+ * [RECOMMENDED] Oper Access Config
+ *
+ * This section is used to set up staff access to restricted oper only commands.
+ * You may define groups of commands and privileges, as well as who may use them.
+ *
+ * The block is recommended, as without it, you will be unable to access most oper commands.
+ * It replaces the old ServicesRoot directive, amongst others.
+ *
+ * Note that third party modules may add additional commands and privileges to this list.
+ *
+ * Available privileges:
+ *  botserv/administration        - Can perform certain BotServ administrative tasks
+ *  chanserv/access/modify        - Can modify channel access lists
+ *  chanserv/auspex               - Can see any informations on /chanserv info
+ *  chanserv/no-register-limit    - May register an unlimited number of channels and nicknames
+ *  chanserv/set                  - Can modifiy the settings of any channel (incl. changing of the owner and password!)
+ *  hostserv/set                  - Can add/modify/delete any vhost
+ *  memoserv/info                 - Can see any information on /memoserv info
+ *  memoserv/set-limit            - Can set the limit of max stored memos on any user and channel
+ *
+ * Available commands:
+ *   botserv/bot/del       botserv/bot/add       botserv/bot/change  botserv/assign/private
+ *   botserv/botlist       botserv/set/private   botserv/set/nobot
+ *
+ *   chanserv/access/list  chanserv/drop         chanserv/forbid     chanserv/getkey
+ *   chanserv/getpass      chanserv/list         chanserv/logout     chanserv/sendpass
+ *   chanserv/status       chanserv/topic        chanserv/suspend    chanserv/set/noexpire
+ *   chanserv/aop/list
+ *
+ *   memoserv/sendall      memoserv/staff
+ *
+ *   nickserv/getpass      nickserv/sendpass     nickserv/getemail   nickserv/suspend
+ *
+ *   operserv/global       operserv/news         operserv/stats      operserv/kick
+ *   operserv/mode         operserv/session      operserv/modlist    operserv/ignore
+ *   operserv/chankill     operserv/akill        operserv/sqline     operserv/sgline
+ *   operserv/szline       operserv/clearmodes   operserv/staff      operserv/defcon
+ *   operserv/modload      operserv/jupe         operserv/set        operserv/noop
+ *   operserv/quit         operserv/update       operserv/reload     operserv/restart
+ *   operserv/shutdown
+ *
+ * First, we define 'opertypes', which are named whatever we want ('Network Administrator', etc).
+ * These can contain commands for oper-only strings (see above) which grants access to that specific command,
+ * and privileges (which grant access to more general permissions for the named area).
+ * Wildcard entries are permitted for both, e.g. 'commands = "operserv/*"' for all OperServ commands.
+ *
+ * Below are some default example types, but this is by no means exhaustive,
+ * and it is recommended that you configure them to your liking.
+ */
+opertype
+{
+	// The name of this opertype
+	name = "Services Root"
+
+	// What commands (see above) this opertype may use
+	commands = "*"
+
+	// What privs (see above) this opertype has
+	privs = "*"
+}
+
+opertype
+{
+	name = "Services Administrator"
+	commands = "operserv/global operserv/news operserv/stats operserv/kick operserv/mode operserv/session operserv/modlist operserv/ignore operserv/chankill operserv/akill operserv/sqline operserv/sgline operserv/szline operserv/clearmodes operserv/staff operserv/defcon botserv/* chanserv/* nickserv/* memoserv/*"
+	privs = "*"
+}
+
+opertype
+{
+	name ="Helper"
+	privs ="hostserv/set"
+}
+
+/*
+ * After defining different types of operators in the above opertype section, we now define who is in these groups
+ * through 'oper' blocks, similar to ircd access.
+ *
+ * The default is to comment these out (so NOBODY will have Services access).
+ * You probably want to add yourself and a few other people at minimum.
+ *
+ * As with all permissions, make sure to only give trustworthy people access to Services.
+ */
+#oper
+#{
+#	// The nickname of this services oper
+#	name = "DukePyrolator"
+#
+#	// The opertype this person will have
+#	type = "Services Root"
+#}#
+#
+#oper
+#{
+#	name = "nick1"
+#	type = "Services Administrator"
+#}#
+#
+#oper
+#{
+#	name = "nick2"
+#	type = "Helper"
+#}
+
 /*
  * [OPTIONAL] Mail Config
  *