1. Registering a
channel
2. Dropping a
channel
3. Identifying
as a channel's founder
4. Retrieving a
password
5. Adding/removing/listing
SOps
6. Adding/removing/listing
AOps
7. Adding/removing/listing
AKicks
8. Oping /
Deoping people
9. Mass kicking
a channel
10. Mass Deoping
a channel
11. Setting
options in channels
a) Changing channel founders
b) Changing channel passwords
c) Changing channel description
d) Changing the channel modes
e) Setting OPGUARD
f) Setting KEEPTOPIC
g) Setting a URL
h) Ops have to identify before
getting opped
i) Restricting a channel to AOps
and higher
j) Turning VERBOSE on and off
k) Setting who can change the topic
l) Allowing users who join first to
stay opped
m) Founder does not need to identify
n) Making the channel private
o) Setting who may send
channel-wide memos
p) Setting the successor of the
channel
q) Setting the web password for the
channel
r) Setting the mailblock option for
the channel
12.
Inviting yourself into the channel
13. Viewing
the access of a person
14. Why a
person opped
15. Unbanning
yourself and others
16. Counting
AOps/SOps and AKicks
17. Finding
information on a channel
18. Channel
Security
SYNTAX:
/chanserv REGISTER < #channel >
< password > < description
>
INFORMATION: The REGISTER command
allows a user to register his/her channel (if it is
not already registered) quickly and painlessly by
typing one line. In order to register a channel, the
user must specify the channel, the password that he or
she, and a short description of his channel.
In order to find out if a channel is registered or
not, type /chanserv info #channel, more on that later.
Also, do not forget to use the # sign when registering
a channel.
EXAMPLE: /chanserv register #channel dt3456 My
chat house.
This would register the channel #channel with
the password dt3456 (a pretty complex
password for someone to just guess out of the blue)
and the description "My chat house."
Back
to Top
SYNTAX:
/chanserv DROP <#channel> <[dropcode]>
INFORMATION: This command will allow
you to drop a channel you are a founder of. You must
first use the command alone and then you will receive
a drop code which you type in with the command.
NOTE: You must identify to the
channel before being able to drop it.
EXAMPLE: /chanserv drop #channel
This is the initial command, after which I would see
something like this in my status window:
-ChanServ- Dropping a channel is permanent and cannot
be undone! "
-ChanServ- To confirm, type: /chanserv DROP #channel
1315098009
After that, I would type the command " /chanserv
DROP #channel 1315098009 " to finalize
if I was sure.
Back
to Top
SYNTAX:
/chanserv IDENTIFY <#channel> <password>
INFORMATION: The identify command
identifies the user as the founder of that channel and
gives the user access to founder-based commands.You
may also use:
/Identify #channel password
Or /services
identify #channel password (This may not work
on some clients).
Back
to Top
4.
Retrieving a password
SYNTAX: /chanserv
sendpass <#channel> <email>
INFORMATION: The sendpass command
allows the founder to have his channel password sent
to the email address associated with the channel in
the services database. Using that function, the
founder may have his password sent to him incase of a
lost/forgotten password.
EXAMPLE: /chanserv sendpass #channel
presentemail@emailaddress.com
NOTE: It is suggested that you set your email address
to a permanent email address that will not change over
time (not an email that came with your ISP, as you may
change ISPs in the future). If your email is changed
and you have lost your password, you will not be able
to retrieve it.
Back
to Top
5.
Adding/removing/listing SOps
SYNTAX: /chanserv sop <#channel>
<add/del/list/wipe> <[nick]>
INFORMATION: The command allows the founder to add or
remove a SuperOP to the channel access list. The list
command, however, can be accessed by AOps' and up.
NOTE: SOps have access to very important commands (AOp
additions and removal, akick addition/removal, etc...)
and therefore should be picked very carefully. You may
not have more than 100 SOps on ChanServ's access list.
Wipe may only be used by founder.
EXAMPLE:" /chanserv sop
#channel add Fieroo "
This will add Fieroo to sop list of
#channel
" /chanserv sop #channel del esteem "
This will del esteem form sop list of
#channel
" /chanserv sop #channel list "
This will list all the sop's in #channel
" /chanserv sop #channel wipe "
This will wipe all sop's in #channel
NOTE: All above example commands can
be used only by FOUNDER or a person who has
identified
to the channel with channel password
Back
to Top
6.
Adding/removing/listing AOps
SYNTAX: /chanserv aop <#channel>
<add/del/list/wipe> <[nick]>
INFORMATION: This command lets any
SOp or the Founder add or remove auto ops from the
channel. The LIST argument in the command can be
accessed by AOps and up.
NOTE: The AOp list is limited to 300
entries. Wipe command may only be used by
founder
EXAMPLE:
"
/chanserv Aop #channel add Fieroo "
This will add Fieroo to Aop list of
#channel
" /chanserv Aop #channel del esteem " This
will del esteem form Aop list of
#channel
" /chanserv Aop #channel list " This
will list all the Aop's in #channel
" /chanserv Aop #channel wipe " This
will wipe all Aop's in #channel
Back
to Top
7.
Adding/removing/listing AKicks
SYNTAX:" /chanserv akick <#channel>
<add/del/list/wipe> <[nick/host]>"
INFORMATION: Akicks are Auto Kicks
and may be added by a SOp or Founder; however only a
founder may wipe akicks. Akicks can be added by
nickname or hostname. Also, you may specify list
patterns
(*word*). Wipe may only be used by founder.
EXAMPLE:
/chanserv
akick #channel add esteem
/chanserv akick #channel add *!*@202.202.202.202
/chanserv akick #channel add *!*whore*@*
/chanserv akick #channel del esteem
/chanserv akick #channel del *!*@202.202.202.202
/chanserv akick #channel del *!*whore*@*
/chanserv akick #channel list
/chanserv akick #channel wipe
NOTE: Only a founder may wipe akicks.
Akicks may be added or deleted by a SOp or Founder
MASKS: can be any word, wildcards accepted
EXAMPLE OF MASKS:
Vishu
(nick)
*Fieroo*!*@* (nick)
*!serv@* (ident)
*!*serv*@* (ident)
*!*@100.100.100.100 (Ip)
*!*@100.100.100.* (Sub Net)
Back
to Top
8.
Oping / Deoping people
SYNTAX:" /chanserv op/deop
<#channel> <nickname(s)>"
INFORMATION: This command is pretty
simple, it allows you to op or deop a nickname in a
channel without having to be opped or even be in the
channel. You must be an AOp or higher in order to use
this command.
EXAMPLE:
/chanserv
op #channel esteem
/chanserv op #channel esteem Fieroo Vishu JanVi Indian
/chanserv deop #channel esteem
/chanserv deop #channel esteem Fieroo Vishu JanVi
Indian
NOTE:
You may not deop someone who has higher
ChanServ access than you. At a time u can op or deop 6
users.
Back
to Top
9.
Mass kicking a channel
SYNTAX: /chanserv mkick #channel
INFORMATION: The MKick (Mass Kick) command is used in
case of a desync in which case the channel has to be
closed and reopened. We request You guys not to misuse
this command.
EXAMPLE: /chanserv mkick #channel
NOTE: The command may not be used if
someone higher than you is in the channel. (e.g. AOps
can't mkick when a SOp is present, SOps can't mkick
when the founder is present).
Back
to Top
10.
Mass Deoping a channel
SYNTAX: /chanserv mdeop <#channel>
EXAMPLE: /chanserv mdeop #channel
INFORMATION: The MDEOP command will
deop everyone in the channel who have equal or less
access in ChanServ than the person using the command.
(e.g. AOps can only deop regular ops and other Ops,
SOps
can only deop other SOps, AOps and the regular ops.)
Back
to Top
11.
Setting options in channels
The SET command has many different
arguments including FOUNDER, PASSWD, DESC,
MLOCK, OPGUARD, KEEPTOPIC, URL, IDENT, RESTRICT and
VERBOSE . All these commands will
modify and change how ChanServ acts in your channel
and you should take some time to get familiar with
them as they will help you in keeping your channel
secure.
NOTE: To use the ChanServ SET command and its
arguments, make sure you are identified as the channel
founder (more below).
a)
Changing channel founders
SYNTAX: /chanserv set <#channel> FOUNDER
INFORMATION: The FOUNDER argument of
the set command will allow the
user that uses this command to change the channel
founder to himself.
EXAMPLE: First identify as the
channel founder. Then change your nick to which u
wanna set as a channel FOUNDER. (registered nick)
(I.e)" /Nick esteem " (I
have identified for my nick)
Then type:" /chanserv set #channel
FOUNDER "
Now the nick esteem is set as the FOUNDER to #channel
NOTE: The nickname that the user is
using must be registered or the command will not work.
Make sure you identify to channel founder before using
the above command.
Back
to Top
b)
Changing channel passwords
SYNTAX: /chanserv set <#channel> PASSWD
<currentpassword> <newpassword>
INFORMATION: This argument will
change the password of the channel from an current
password to a new password. It is a good idea to
rotate your password once every few months to improve
security.
EXAMPLE: /chanserv set #channel PASSWD dt3456
dt345678
This command will set the channel password from dt3456
to dt345678
Back
to Top
c)
Changing channel description
SYNTAX: /chanserv set <#channel> DESC
< newdescription>
INFORMATION: The DESC argument lets a user change the
description of his or her channel which can be viewed
through the /chanserv info command (more on that
later).
EXAMPLE: /chanserv set #channel DESC V Come In
Peace!
This command will change #channel 's channel
description to 'V Come In Peace!'
Back
to Top
d)
Changing the channel modes
SYNTAX: /chanserv set <#channel> MLOCK
<modes>
INFORMATION: The MLOCK command is one of the most
important commands to maintain channel security. Below
is a list of all the possible modes and what they do:
+R - Only registered nicks allowed.
Very useful if you wish to stop clone attacks, since
most clone attacks use unregistered nicks.
+n - No external messages. This
option prevents people who are not in channel from
sending messages to that channel.
+t - Only ops set topic. This command
will make sure non-ops cannot change the topic of the
channel. There are also a few ChanServ settings that
can help with more specific topic settings (only SOps/AOps
can change topic) , more on that below.
+s AND +p - Both commands set the
channel to be invisible in /list commands, but +s also
sets it invisible in whois, both settings are a good
way to keep unwanted users out of channel.
+i - This option makes the channel
closed to anyone unless an op invites them or they
have ChanServ invite them using the /chanserv invite
command.
+k - This option sets a password on
the channel which a user must type in order to join.
+l - This option limits the amount of
users that may join the channel. Some bots have
scripts that set the limit to be 5-10 users more than
the channel has at a time, which is a good technique
for clone protection. (More on that in mode help
section).
+m - This option prevents anyone who
is not voiced or Opped from talking in the channel.
+M
- Only registered nicks are allowed to talk
on mains. Very useful if you wish to stop clone
attacks, since most clone attacks use
unregistered nicks.
+c - This option will disable any
control codes (color, bold, underline, reverse) from
being sent to the channel and will those messages.
Also useful against clone attacks.
NOTE: Some of the options require another
argument (i.e. +l needs a number, +k needs a password)
so the arguments need to be specified in the order of
the options. (i.e. +kl password number)
EXAMPLE: /chanserv set #channel MLOCK +ntR-s
This command would set #channel to +ntR-s
which means only ops can change topic, no external
messages, registered nicks only and secret can't be
set.
/chanserv set #channel MLOCK +nts-miRckpl
This command would set #channel to +nts-miRckpl
which means only ops can change topic, no external
messages and secret only. non moderated, its not
invite only, any nicks can join (it need not be only
registered nicks), Colorful (can use colours), non key
mode, channel is not private, it is not limited (any
number of users can join).
Back
to Top
e) Setting OPGUARD
on and off
SYNTAX: /chanserv <set> <#channel>
OPGUARD <on/off>
INFORMATION: When this argument is set on only AOps,
SOps and the Founder will be allowed to be an op in
the channel, everyone else will automatically be
deopped.
EXAMPLE:
/chanserv
set #channel OPGUARD on
/chanserv set #channel OPGUARD off
Back
to Top
f) Setting
KEEPTOPIC on and off
SYNTAX: /chanserv set <#channel>
KEEPTOPIC <on/off>
INFORMATION: If a channel becomes empty (last person
leaves), ChanServ will save the topic if this option
is set on so that next time someone comes in the topic
will be recreated with the nick who set it.
Back
to Top
g)
Making a URL show in the info
SYNTAX: /chanserv set <#channel> URL
<[URLhere]>
INFORMATION: This command lets you set the URL for
your channel which can be viewed through the /chanserv
info command. To remove a URL, type the command
without a URL at the end.
Back
to Top
h)
Ops have to identify before getting opped
SYNTAX: /chanserv set <#channel> IDENT
<on/off>
INFORMATION: The ident argument regulates whether
people can get opped in the channel automatically
without having to identify (access list) or must
identify.
Back
to Top
i)
Restricting a channel to AOps and higher
SYNTAX: /chanserv set <#channel>
RESTRICT <on/off>
INFORMATION: The RESTRICT argument, when set on, will
not allow anyone who is not on the channel access list
to join the channel and will automatically kick and
ban them.
Back
to Top
j) Turning VERBOSE
on and off
SYNTAX: /chanserv set <#channel> VERBOSE
<on/off>
INFORMATION: The VERBOSE argument, when set on, will
notify channel ops of any changes made to the channel
access list (ie. aop added/removed, sop added/removed,
akick added/removed).
An example of output would be:
-ChanServ:@#channel- [VERBOSE] esteem!Falcon@202.142.100.189
=> aop #channel add Fieroo
Back
to Top
k) Setting who can
change the topic
SYNTAX: /chanserv set <#channel>
TOPICLOCK <founder/sop/off>
INFORMATION: The TOPICLOCK command, when turned on,
will allow you to set who should be able to change the
topic: You (the founder), a SOp, or anyone else (off).
Back
to Top
l)
Allowing users who join to stay opped (leaveops)
SYNTAX: /chanserv set <#channel>
LEAVEOPS <on/off>
INFORMATION: This command, when turned on, will not
deop the first user to join the channel regardless of
whether he is an op or not, if set off (as it is by
default), it will deop anyone who is not AOp or
higher. It is recommended you leave this setting
untouched for security.
Back
to Top
m) Founder does not need
to identify (unsecure)
SYNTAX: /chanserv set <#channel>
UNSECURE <on/off>
INFORMATION: This command, when turned on, will allow
anyone on the founder's nick access list to make
founder type changes to the channel. This may be a
large security compromise if the founder does not have
a very secure nickserv access list. It is suggested to
leave this argument untouched.
Back
to Top
n)
Making the channel private
SYNTAX: /chanserv set <#channel> PRIVATE
<on/off>
INFORMATION: This setting, when turned on, will
prevent the /chanserv invite command from being used.
It will also allow only people who know about the
channel to access it.
Back
to Top
o)
Setting who may send channel-wide memos
SYNTAX: /chanserv set <#channel> MEMO
<none/aop/sop/founder>
INFORMATION: This command allows the founder to manage
who may send channel memos. When memo is set to none,
no one can memo; when memo is set to AOp, all people
on chanserv's access list may memo, when
memo is set to SOp only founder and sops may memo and
when the option is set to founder only the channel
founder may send channel wide memos.
EXAMPLE:
/chanserv
set #channel MEMO none
/chanserv set #channel MEMO aop
/chanserv set #channel MEMO sop
/chanserv set #channel MEMO founder
Back
to Top
p)
Setting the successor of the channel
SYNTAX: /chanserv set <#channel>
SUCCESSOR < nickname / - >
INFORMATION: This command allows the founder to set
the successor for the channel in case the nickname of
the founder expires. When and if the nickname expires
the channel will be turned over to the successor with
all rights and privileges of the founder. If you wish
to set the successor to no-one, use a hyphen
("-") instead of a
nickname.
EXAMPLE: /chanserv set #channel SUCCESSOR
esteem
That will esteem as the successor of #channel
/chanserv set #channel SUCCESSOR -
That will leave the successor list empty (no-one)
Back
to Top
q)
Setting the web password for the channel
SYNTAX: /chanserv set <#channel>
WEBPASSWD <password>
INFORMATION: This command allows the founder to set
the web password for his channel's website on the web
(see the Web hosting Services document at http://help.dal.net/docs/webhost.html
for more information on channel websites).
NOTE: The password should be different from the
password of the channel so that it may be given out to
people in order to modify the website.
Back
to Top
r)
Setting the mailblock option for the channel
SYNTAX: /chanserv set <#channel>
MAILBLOCK <on/off>
INFORMATION: This command allows the founder of a
channel to turn on/off mailblock on his channel, by
that enabling/disabling the option for the channel
password to be sent to the email on file in case of a
lost password.
NOTE: By enabling this command, the founder no longer
has the option to retrieve his password incase it is
lost/forgotten. The mailblock option should NOT be
turned on unless the founder is absolutely sure that
he is not going to forget/lose the password.
Back
to Top
12.
Inviting yourself into the channel
SYNTAX: /chanserv invite <#channel>
INFORMATION: This command will invite you into a
+R/+O/+i/+l/+k/+b channel or a channel which you have
been banned from by someone. You must be an AOp or
higher to use that command.
Back
to Top
13.
Viewing the access of a person
SYNTAX: /chanserv acc/access <#channel>
<[nick]>
INFORMATION: This command lets an AOp or higher see
what access he/someone else has to the channel. The
access is displayed numerically, below are the
definitions:
-2 = Channel is frozen or closed
-1 = AutoKICKed from the channel
0 = basic
1 = Aop
2 = Sop
3 = Has founder access via a NickServ
access list mask
4 = Has founder access via
identification to NickServ
5 = Has founder access via
identification to ChanServ
If the USER is not online, the access will be
0.
NOTE: You must be an AOp or higher to use that
command.
EXAMPLE: /chanserv acc #channel esteem
The following reply would come from ChanServ:
-ChanServ- esteem ACC #channel 1 (aop)
Back
to Top
14.
Why a person opped
SYNTAX: /chanserv WHY <#channel>
<nick>
INFORMATION: The WHY command does the same thing as
the ACC/ACCESS command, however it returns the status
of the user in AOp/SOp/Founder form with no access
level. It will also tell you when someone is using a
different nickname what nickname he has access to that
let him become opped.
NOTE: You must be an AOp or higher to use that
command
EXAMPLE: /chanserv why #channel esteem
Below is what you would receive from ChanServ
" -ChanServ- esteem has Aop access to
#channel. Reason: Identification to services with the
Nick password. "
Back
to Top
15.
Unbanning yourself and others
SYNTAX: /chanserv unban <#channel>
<[nick/*/host]>
INFORMATION The UNBAN command will unban all masks
that match your nick!user@host if you do not specify a
nickname. AOps may also unban a specific user or a
host. SOps can unban everything by specifying
the * sign instead of a nickname.
EXAMPLE:
"
/chanserv unban #channel esteem "
Will unban any matching bans on the nick esteem
" /chanserv unban #channel * "
will unban all bans in #channel, u should be Sop or
Founder
" /chanserv unban #channel
*!Falcon@202.142.100.* "
will unban that mask
Back
to Top
16.
Counting AOps/SOps and AKicks
SYNTAX: /chanserv count <#channel>
INFORMATION: This command counts all the AKicks, AOps
and SOps in a channel and gives you the number in a
reply.
EXAMPLE: /chanserv count #channel
This will return the following:
" -ChanServ- Channel: #channel - AOP: 57
SOP: 15 AKICK: 19 "
Back
to Top
17.
Finding information on a channel
SYNTAX:
/chanserv info <#channel>
INFORMATION: The INFO command allows one to see
specific information about channels (chanserv
settings, topic, registry date, last op date, etc.)
EXAMPLE: /chanserv info #channel
This command will give out the following information:
"-ChanServ- Info for #channel:
"-ChanServ- Founder : esteem
(Falcon@202.202.202.202) "
"-ChanServ- Mode Lock : +ntmc-silkR "
"-ChanServ- Description: Channel of Rock Lovers!.
"
"-ChanServ- Options : Verbose,ident "
"-ChanServ- Memo Level : SOP "
"-ChanServ- Registered : Thu 02/23/1997 02:07:00
GMT "
"-ChanServ- Last opping: Sat 11/13/2001 11:53:18
GMT "
"-ChanServ- *** End of Info ***"
This shows that the founder is esteem with the host
Falcon@202.202.202.202, the channel modes are +ntmc-silkR,
the description is 'V Come In Peace.' Options
verbose,ident. Memo level Sop..etc
Back
to Top
18.
Some Tips
1) Make your password, use uppercase and
lowercase letters, as well as numbers. This makes
passwords much harder to guess.
2) NEVER EVER give out your password to anyone who you
wouldn't trust with your life. DALnet does NOT help
users who shared their password and later found it
misused.
3) Add SOps very carefully. Also, add AOps very
carefully. Don't add anyone who you don't know very
well to the OP list.
4) By default, set an mlock of at least +nt. This will
prevent people from changing your topic or messaging
without being in the channel.
5) Don't create an auto-identify script. If you do,
make sure you don't give out the script with the auto
identify or you may be in serious trouble.
6) Rotate your password at least once every couple of
months.
That's about it. *Peace*
Special
Thanks to DALnet Network
|
