| 1 |
_ _ _ _ ___ |
| 2 |
/_\ (_)_ __ __| |_ __ ___ _ __ /\ \ \/ _ \ |
| 3 |
//_\\| | '__/ _` | '__/ _ \| '_ \ _____ / \/ / /_\/ |
| 4 |
/ _ \ | | | (_| | | | (_) | |_) |_____/ /\ / /_\\ |
| 5 |
\_/ \_/_|_| \__,_|_| \___/| .__/ \_\ \/\____/ |
| 6 |
|_| |
| 7 |
README |
| 8 |
|
| 9 |
Airdrop-ng is a rule based Deauth Tool |
| 10 |
|
| 11 |
Readme Written by Mubix & TheX1le |
| 12 |
|
| 13 |
##################################################### |
| 14 |
|
| 15 |
# Dependencies and Installation # |
| 16 |
|
| 17 |
##################################################### |
| 18 |
|
| 19 |
Requires python 2.7 for the installer to work, unless you edit it and remove the "--prefix " part. |
| 20 |
|
| 21 |
Dependencies: |
| 22 |
|
| 23 |
[*] lorcon |
| 24 |
[*] Pylorcon2 |
| 25 |
[*] A lorcon supported wireless card (mac80211 drivers) with monitor mode and injection |
| 26 |
|
| 27 |
********************** |
| 28 |
* Installing lorcon * |
| 29 |
********************** |
| 30 |
|
| 31 |
You can get lorcon source from: |
| 32 |
|
| 33 |
[*] git clone https://github.com/kismetwireless/lorcon |
| 34 |
|
| 35 |
Then you will have to compile it: |
| 36 |
|
| 37 |
[*] cd lorcon && ./configure && make && make install |
| 38 |
|
| 39 |
Next compile Pylorcon2 source |
| 40 |
|
| 41 |
[*] cd pylorcon2 && python setup.py install |
| 42 |
|
| 43 |
If pylorcon reports import errors you need to run the following command: |
| 44 |
|
| 45 |
[*] ln -s /usr/local/lib/liborcon-2.0.0.so /usr/lib |
| 46 |
|
| 47 |
This will create a symlink to the directory that pylorcon looks in for |
| 48 |
liborcon. |
| 49 |
|
| 50 |
If you are on ubuntu you will also need to install the python-dev |
| 51 |
package as they do not include the headers |
| 52 |
##################################################### |
| 53 |
|
| 54 |
# Usage and Options # |
| 55 |
|
| 56 |
##################################################### |
| 57 |
|
| 58 |
-t |
| 59 |
|
| 60 |
Airodump-ng CSV file location. |
| 61 |
|
| 62 |
It is highly recommended that you have Airodump-ng ACTIVELY RUNNING |
| 63 |
|
| 64 |
before and while you run Airdrop-ng. You should run Airodump-ng with |
| 65 |
|
| 66 |
the following options: |
| 67 |
|
| 68 |
# airodump-ng <interface> --write <filename(no extension)> |
| 69 |
--output-format csv |
| 70 |
|
| 71 |
# EXAMPLE: airodump-ng wlan0 -w capture --output-format csv |
| 72 |
|
| 73 |
# this will write capture-01.csv to the current working directory |
| 74 |
|
| 75 |
-r |
| 76 |
|
| 77 |
Rule set config file location. |
| 78 |
|
| 79 |
docs/dropRules.conf.example contains several examples on how construct |
| 80 |
|
| 81 |
your rules please take a look at this file. The Rules are the core of |
| 82 |
what |
| 83 |
|
| 84 |
makes airdrop-ng so special and determine what clients get a kick and |
| 85 |
which |
| 86 |
|
| 87 |
ones are saved. |
| 88 |
|
| 89 |
Rules are run cascading order so make sure your allows are written |
| 90 |
before your denys. |
| 91 |
|
| 92 |
Adding a # to the front of a line comments out the line |
| 93 |
|
| 94 |
NOTE: The a/any|any rule... This rule currently causes the program to |
| 95 |
exit |
| 96 |
|
| 97 |
with a error message. This is by design as the tool allows by default. |
| 98 |
|
| 99 |
NOTE: By default if no rule exist for a client or ap airdrop-ng assumes |
| 100 |
that |
| 101 |
|
| 102 |
you wish to allow it. This can be changed by putting a d/any|any |
| 103 |
|
| 104 |
##################################################### |
| 105 |
|
| 106 |
# Advanced Rule Writing # |
| 107 |
|
| 108 |
##################################################### |
| 109 |
|
| 110 |
Rules based on OUI: |
| 111 |
|
| 112 |
Currently it only supports the company name or a single OUI, the format |
| 113 |
is as follows: |
| 114 |
|
| 115 |
Company name |
| 116 |
|
| 117 |
a or d /bssid or any|company name;company name; company name |
| 118 |
|
| 119 |
EXAMPLE: d/any|apple |
| 120 |
|
| 121 |
This example attacks only devices with OUI's matching "Apple" |
| 122 |
|
| 123 |
Notice the ; as a delimiter for company names this is because many |
| 124 |
company |
| 125 |
|
| 126 |
names contain comas. When writing rules make sure you check the oui.txt |
| 127 |
|
| 128 |
file in the support directory. There isn't a standard for company names. |
| 129 |
|
| 130 |
For example "Apple" has 11 unique names in the file. If you check the |
| 131 |
|
| 132 |
Apple.sample.txt file in the support directory you can see a list of |
| 133 |
|
| 134 |
each one of them. |
| 135 |
|
| 136 |
For all OUIs to be used you would need to write a rule that contained |
| 137 |
|
| 138 |
each company name. A newer and easier way is to use the built in regex |
| 139 |
|
| 140 |
function. Airdrop-ng will attempt to find all of company names for you a |
| 141 |
|
| 142 |
sample rule using this is: |
| 143 |
|
| 144 |
d/any|Sony Corporation |
| 145 |
|
| 146 |
or even better: |
| 147 |
|
| 148 |
d/any|sony |
| 149 |
|
| 150 |
The same can be done in the bssid field |
| 151 |
|
| 152 |
d/sony|any |
| 153 |
|
| 154 |
d/broadcom|apple |
| 155 |
|
| 156 |
The above example would kick any apple device off a broadcom radio AP |
| 157 |
|
| 158 |
The regular expression function is NOT case sensitive. This option while |
| 159 |
|
| 160 |
much faster only works well with companies that support proprietary |
| 161 |
hardware |
| 162 |
|
| 163 |
like Apple or Sony. This is not to say it won't work with others but it |
| 164 |
works |
| 165 |
|
| 166 |
best on proprietary hardware. |
| 167 |
|
| 168 |
Rules written in this manner will match all OUI's found for that company |
| 169 |
name |
| 170 |
|
| 171 |
Matching a single OUI |
| 172 |
|
| 173 |
Example: |
| 174 |
|
| 175 |
d/00:50:E4|any |
| 176 |
|
| 177 |
This rule will match any bssid that 00:50:E4 as an OUI and kick any |
| 178 |
clients attached to it |
| 179 |
|
| 180 |
The same can be done in the client field |
| 181 |
|
| 182 |
d/any|00:50:E4 |
| 183 |
|
| 184 |
Note: doing a single OUI will match only that OUI. |
| 185 |
|
| 186 |
Note: You can mix and match rule types IE |
| 187 |
|
| 188 |
d/apple|00:21:E9:3D:EB:45,00:17:AB:5C:DE:3A,00:1B:63:00:60:C4 |
| 189 |
|
| 190 |
Or |
| 191 |
|
| 192 |
a/00:1B:63:00:60:C4|apple |
| 193 |
|
| 194 |
However it is not wise to try to mix and match rule types for example |
| 195 |
|
| 196 |
d/apple|00:21:E9:3D:EB:45,00:17:AB:5C:DE:3A,sony |
| 197 |
|
| 198 |
|
| 199 |
this confuses the current parser and makes it unhappy |
| 200 |
|
| 201 |
You can complete the same thing with two rules IE |
| 202 |
|
| 203 |
d/apple|00:21:E9:3D:EB:45,00:17:AB:5C:DE:3A |
| 204 |
|
| 205 |
d/apple|sony |
| 206 |
|
| 207 |
Airdrop-ng works in a loop |
| 208 |
|
| 209 |
Each time the program finishes sending packets it re-parses the airodump |
| 210 |
file |
| 211 |
|
| 212 |
for changes as well as the rule file. This means that it possible to |
| 213 |
update |
| 214 |
|
| 215 |
rules while the program is running. |
| 216 |
|
| 217 |
Happy hacking! |