April,14 2007

Hello,

We have a docs file who needs to be updated, because the MLOCK command has been changed
Go to the directory http://docs.dal.net/xml/chanserv/
Choose the english folder
Open http://docs.dal.net/xml/chanserv/en/chanserv-1.1.5.xml , then go to the sections 11.4 (Changing the channel modes).
This section must be changed (in your language) to:

<section>
<title>Changing the channel modes</title>
<emphasis type="strong">Syntax:</emphasis><command> /chanserv set <param>#channel</param> mlock <param>modes</param> </command>

</p><p><emphasis type="strong">Information:</emphasis> 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:

</p><p><emphasis type="strong">+R</emphasis> - Only registered nicks allowed. Very useful if you wish to stop clone attacks, since most clone attacks use unregistered nicks.

</p><p><emphasis type="strong">+n</emphasis> - No external messages. This option prevents people who are not in channel from sending messages to that channel. 

</p><p><emphasis type="strong">+t</emphasis> - 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.

</p><p><emphasis type="strong">+s and +p </emphasis>- Both commands set the channel to be invisible in /list commands, but +s also sets it invisible in whois, both settigs are a good way to keep unwanted users out of channel.

</p><p><emphasis type="strong">+i</emphasis> - This option makes the channel closed to anyone unless an op invites them or they have ChanServ invite them using the /chanserv invite command.

</p><p><emphasis type="strong">+m</emphasis> - This option prevents anyone who is not voiced or OPed from talking in the channel.

</p><p><emphasis type="strong">+c</emphasis> - 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.

</p><p>

For more information on modes check out <url>http://docs.dal.net/docs/modes.html</url>

</p><p>

</p><p><emphasis type="strong">Note:</emphasis> Some of the options require another argument (ie. +l needs a number, +k needs a password) so the arguments need to be specified in the order of the options. (ie. +kl password number) 

</p><p><emphasis type="strong">Example:</emphasis><command> /chanserv set #mystro mlock +ntR-s </command>

</p><p></p><p> This command would set #mystro to +ntR-s which means only ops can change topic, no external messages, registered nicks only and secret can't be set. 

</p>

</subsection>

This is for section 11.4 and for sections 18 (Channel Security) must be changed to:

<title>Channel Security</title>

<p>

Now that you have gotten yourself familiarized with the ChanServ commands, it's time to move on to a very important topic: Channel Security.

Each day, many people join channels such as #operhelp in order to receive help with channel takeovers, forgotten passwords, etc...

Here are some tactics to help you fight all of the security problems. 

</p><p>

1) Make your password use uppercase and lowercase letters, as well as numbers. This makes passwords much harder to guess. 

</p><p>

2) <emphasis type="strong">NEVER EVER</emphasis> give out your password to anyone who you wouldn't trust with your life. DALnet does <emphasis type="strong">not</emphasis> help users who shared their password and later found it misused.

</p><p>

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. 

</p><p>

4) Once the channel is registed , Chanserv set +nt-k as MLOCK ,So if you want to set a password for your Channel , you have to remove the -k from the MLOCK and keep the +nt for channel protection , Syntex of removal the MLOCK is : /chanserv set #channelname mlock +nt 

</p><p>

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. 

</p><p>

6) Rotate your password at least once every couple of months.

</p><p></p><p>

That's about it. You may want to take a look at the Passwords document (<url>http://docs.dal.net/docs/passwords.html</url>) for more information on passwords. 

</p></section>

The new file must be saved as chanservxx-1.1.6.xml (where xx is your language acronym). 
That's all :)
Thank you.
Zappu if you have any question about the document please mail me at zappu.dalnet@gmail.com