Update example conf to new way of using oper password hashing

git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@5881 e03df62e-2008-0410-955e-edbf42e46eb7

1 files changed, 13 insertions, 5 deletions

diff --git a/docs/inspircd.conf.example b/docs/inspircd.conf.example
index 172eb7a97..23d6eefbf 100644
--- a/docs/inspircd.conf.example
+++ b/docs/inspircd.conf.example
@@ -1252,17 +1252,25 @@
 
 #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
 # Oper hash module: Allows hashed oper passwords
-# Relies on the module m_md5.so or m_sha256.so being loaded before
+# Relies on the module m_md5.so and/or m_sha256.so being loaded before
 # m_oper_hash.so in the configuration file.
 #<module name="m_oper_hash.so">
 #
 #-#-#-#-#-#-#-#-#-#-# OPER HASH CONFIGURATION #-#-#-#-#-#-#-#-#-#-#-#-#
 #
-# To use this module, you must define which hashing algorithm you want
-# to use. This must correspond to either of m_sha256.so or m_md5.so
-# modules that you have loaded.
+# To use this module, you must define a hash type for each oper's
+# password you want to hash. For example:
 #
-#<operhash algorithm="md5">
+#     <oper name="katsklaw"
+#           host="ident@dialup15.isp.com"
+#           hash="sha256"
+#           password="a41d730937a53b79f788c0ab13e9e1d5"
+#           type="NetAdmin">
+# 
+# The types of hashing available vary depending on which hashing modules
+# you load, but usually if you load m_sha256.so and m_md5.so, both md5
+# and sha256 type hashing will be available (the most secure of which
+# is SHA256).
 
 #-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#
 # Oper Join module: Forces opers to join a channel on oper-up