submission of a page for the site by Ashen

Moonlight <accountnamehere-/[email protected]> Mon, 23 Jun 2003 23:37:16 +0100 (BST)

Newsgroups	gmane.network.irc.blitzed.web
Message-ID	<[email protected]>

Here is a page I wrote on how to recover from a
channel takeover using blitzed.org's irc services.

I have tried to make it conform to the blitzed web
team's standards.

Ashen (NS ID Ashen on irc.blitzed.org, I idle in #blitzed)

________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://uk.messenger.yahoo.com/

takeovers.html (text/html, 8.4 KB)

<?php include=("top.phtml");
blitzed_title("How to recover a channel from takeover"); ?>




<HTML>
<HEAD><TITLE> How to regain your channel after a takeover </TITLE></HEAD>
<BODY>
<B>------- How to reverse a channel takeover on irc.blitzed.org's network ---------</B><BR>
<BR>
In order to take over a channel, ops are needed, now, ops can be gained by one of 4 methods:<BR>
being the channel founder, being a channel SOP, being a channel AOP, or someone simply using /mode #channel +o user.<BR>
<BR>
In the first case, a channel founder can do whatever they like in their channel, if you don't like it,<BR>
then simply don't stay in that channel, there is no way for any person to reverse what the channel founder does.<BR>
To clarify a related point, Ircops will not intervene in channel affairs, they maintain the network, they generally do not interfere with channels.<BR>
<BR>
How difficult it is to reverse a takeover will depend on what level of access the person doing the takeover had on the channel before they took it over,<BR>
the more access they had the more difficult it will be to remove them and get control of the channel back.<BR>
<BR>
I will deal with the 4 ways the user got the ops they used to take over the channel in order of difficulty, easiest first.<BR>
<BR>
<BR>
<BR>
<B>--- 1 --- How to deal with a user op'ed by someone else that takes over the channel ---</B><BR>
Deop the user that did the takeover, and invite yourself back to the channel if they banned you:<BR>
/msg chanserv deop #channel USER<BR>
/msg chanserv invite #channel<BR>
This should get you back into the channel, and if you are on the AOPs list you will have ops and they won't have, thus the channel is back under your control.<BR>
<BR>
<BR>
<B>--- 2 --- How to deal with an AOP that decides to use their access to take over the channel ---</B><BR>
Unless you are a SOP or above, you can't really do annything, because AOPS can reverse annything other AOPS or below do to them.<BR>
In this situation, contact a SOP or the channel founder, <BR>
you can tell who is a SOP and who the channel founder is by using:<BR>
/msg chanserv access #channel list<BR>
and<BR>
/msg chanserv info #channel<BR>
Any person with an access level of 3 is a VOP (auto voice), with 5 is an AOP (auto ops), and annyone with 10 or above is a SOP (super ops).<BR>
You will get back a few lines of information from the INFO command, one of which will say "Founder: NICK".<BR>
With both of these in hand, you know who can help you, you must find one of these SOPs or the founder.<BR>
Now, once you either have a SOP+ to hand, or if you are one yourself, use<BR>
/msg chanserv access #channel del USER<BR>
to remove that person's access to the channel, once they can't get ops back anymore it should be a simple case like that of -1- that any AOP can deal with by doing<BR>
/msg chanserv deop #channel USER<BR>
/msg chanserv invite #channel<BR>
To deop the user them and let you rejoin, and since chanserv will op any AOP+ on join, you will have control of the channel again.<BR>
<BR>
<BR>
<B>--- 3 --- How to deal with a SOP that tries to takeover the channel ---</B><BR>
This is complex, as a SOP has a lot of access to chanserv, including the ability to remove other people's ops.<BR>
Only the founder can really reverse a takeover done by a SOP, to do this, they must<BR>
/msg chanserv access #channel list <BR>
to find out who is on the access list, and at what level they are on it. This is vital, as a SOP can change the access list,<BR>
and could easily register another nick, and use their SOP access to assign this other nick AOPs, so just deleting their account from chanserv might not be enough.<BR>
The founder would then have to use<BR>
/msg chanserv access #channel del USER<BR>
for each USER that is on the access list but shouldn't be, starting at the highest leveled users and working down,<BR>
as if you delete the lower ones first, the higher can just readd them.<BR>
The founder would then have to use <BR>
/msg chanserv akick #channel view<BR>
to check that the SOP did not put any perm bans on channel that may be used to keep rightful users out, these can be deleted using<BR>
/msg chanserv akick #channel del num<BR>
where 'num' is either the number of the akick, or the mask that it is set for.<BR>
Then, the founder has to deop everyone on channel, and clear out any modes that have been set:<BR>
/msg chanserv clear #channel ops<BR>
/msg chanserv clear #channel modes<BR>
this will remove EVERYONE's ops, users will have to either rejoin or ask chanserv to get ops back.<BR>
The clear modes command will remove all modes that lock up the channel, and since the user doing the takeover can't get ops back to lock the channel again,<BR>
you can now re-enter the channel and you will have control back.<BR>
<BR>
<B>--- 4 --- How do I stop this happening again? ---</B><BR>
Chiefly, don't give out ops, and in particular, **NEVER give access with chanserv** to people you don't know and trust well.<BR>
Sometimes ops will misbehave, or you might get a 'rogue op' situation, in these cases just remove their access, by deoping them and removing their access to chanserv,<BR>
and they can't control the channel any longer. If they then start to flood, attack or otherwise harass the channel, you should ban them just like any other bad user.<BR>
There are options that can be set on chanserv that will enforce a stricter control of the channel, these are:<BR>
/msg chanserv set secure<BR>
and /msg chanserv set secureops<BR>
The first of these should be set on all channels, and is set by default on most networks. It only allows AOP+ users to be recognised if they have identified with nickserv.<BR>
This stops someone inpersonating an AOP in order to get ops for a takeover attempt.<BR>
The second, secureops, changes the rules of the channel so that ONLY AOPs and above may have ops at all, <BR>
if a non AOP gets ops then they will be instantly deop'ed by chanserv, and chanserv's OP command can't be used on them.<BR>
This is a setting some channels make use of to control more strictly who can and who can't be ops,<BR>
and you might like to set this if you are experiencing takeover problems, as it is very good at stopping ops being handed to untrustworthy people.<BR>
<BR>
<BR>
<BR>
<B>--- Appendix of Commands ---</B><BR>
Since some channels are configured with strange settings, these commands might not always work (the founder can change the channel so that these commands<BR>
require different levels of access then the ones they normally do. If this is the case, the founder should have told you about this in advance.)<BR>
Access levels are higherarchial, so you can use the commands of any level up to your own, so a Founder can use AOP, SOP, and Founder commands,<BR>
whereas a SOP can only use SOP and AOP commands, and an AOP can use AOP commands only.<BR>
To get a complete list of what commands are avalible on chanserv, and what access level each requires, try:<BR>
/msg chanserv levels #channel list<BR>
<BR>
<BR>
Founder Commands:<BR>
/msg chanserv clear #channel ops <---- deops all users in channel, AOPS and above can either cyle(join/part) the channel, or ask chanserv, to get ops again.<BR>
/msg chanserv clear #channel modes  <--- removes all restrictive modes such as i,l,k,m etc, that may be used to lock up the channel<BR>
/msg chanserv clear #channel bans  <--- removes all bans that are currently set on the channel<BR>
/msg chanserv set #channel secure on <--- helps to stop illegitimate people getting ops on channel<BR>
/msg chanserv set #channel secureops on <--- allows only AOPs, SOPs and the founder to have ops at all<BR>
<BR>
SOP+ Commands (usually level 10):<BR>
/msg chanserv access #channel del USER <---- deletes USER from access, meaning they won't get ops any more.<BR>
/msg chanserv access #channel add USER -1 <---- makes it so chanserv will never allow USER to be op'ed. If someone ops them, chanserv will deop them.<BR>
<BR>
AOP+ Commands (usually level 5):<BR>
/msg chanserv invite #channel <--- gets an invite to the channel from chanserv, this allows you to walk past bans, invite only modes, etc<BR>
/msg chanserv op #channel USER <---- ops USER, usually a trusted person that can help with securing the channel again<BR>
/msg chanserv deop #channel USER <---- deops USER, usually used on someone who got ops illegally to prevent them harming the channel<BR>
<BR>
This document was made by Ashen, submitted to the Blitzed web team on Mon, Jun 23 2003.<BR>
</BODY>
</HTML>


<?php include("bottom.phtml"); ?>