Debian Codegraph @

docs/Documentation_incomplete.html

raw
1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 <html>
3 <head>
4 <meta content="text/html; charset=ISO-8859-15"
5 http-equiv="content-type">
6 <title>MDK3 Documentation</title>
7 </head>
8 <body>
9 <div style="text-align: center;"><img
10 style="width: 466px; height: 145px;" alt="k2wrlz logo" src="k2wrlz.png"><br>
11 <br>
12 <big style="font-weight: bold;"><big>MDK3 Documentation</big></big><br>
13 <br>
14 <div style="text-align: left;">
15 <div style="text-align: center;">MDK is a proof-of-concept tool to
16 exploit common IEEE 802.11 protocol weaknesses.<br>
17 <span style="text-decoration: underline;">It is your responsibility to
18 make sure you have permission from the network owner before running MDK
19 against it.</span><br>
20 </div>
21 <br>
22 <br>
23 MDK3 is a work from ASPj of k2wrlz, it uses the osdep library from the
24 aircrack-ng project to inject frames on several operating systems.<br>
25 Many parts of it have been contributed by the great aircrack-ng
26 community:<br>
27 <span style="font-weight: bold;">Antragon, moongray, Ace, Zero_Chaos,
28 Hirte, thefkboss, ducttape, telek0miker, Le_Vert, sorbo, Andy Green,
29 bahathir</span><br>
30 THANK YOU!<br>
31 <br>
32 MDK3 is licenced under the GPLv2<br>
33 <br>
34 <br>
35 <big>Contents:<br>
36 1. Setting up your environment<br>
37 2. Getting MDK3 to run (Compiling MDK3, where to get binaries)<br>
38 3. How to use MDK3<br>
39 4. The different test modes</big><br>
40 <br>
41 <br>
42 <br>
43 <big style="font-weight: bold;"><big>1. Setting up your environment<br>
44 </big></big><big><big><br>
45 </big><big><small><small>MDK3 is a tool, that "injects" data into
46 wireless networks. "Injection" is the possibility to send self-made
47 data through the air without being connected or associated to anything.
48 MDK3 is used to send valid and invalid data, that does belong to the
49 wireless management and not to a regular data connection. This is only
50 possible with this Injection technique. Sadly, this is something, wifi
51 equipment is NOT build for! To enable the injection feature on your
52 wireless card, you need modified drivers. A lot of work has already
53 been done by several hackers (including me) to make these modified
54 drivers available for a lot of wifi adaptors.<br>
55 To set up your driver for Injection, please visit <a
56 href="http://www.aircrack-ng.org">www.aircrack-ng.org</a> and follow
57 the Driver Documentation there.<br>
58 MDK3 uses the drivers and Injection routines from this project and its
59 predecessor. Thus, all drivers listed there should work with MDK3.
60 (Some special hardware, like Intel Centrino (ipw2200) is NOT supported
61 since they can only inject data, and no management information!)<br>
62 MDK3 works on Linux and maybe FreeBSD currently, soon it may run on
63 Windows, too. It runs best with a pretty
64 up-to-date kernel and drivers.<br>
65 <br>
66 <br>
67 </small></small></big></big><big style="font-weight: bold;"><big>2.
68 Getting MDK3 to run (Compiling MDK3, where to get binaries)<br>
69 <br>
70 </big></big><big><big><small><small>Some Linux distributions already
71 contain a precompiled mdk3 binary. As far as I know, there are Debian
72 and BackTrack having the old mdk2 in their repositories at the moment.
73 If you do not use one of these, you have
74 to create the binary yourself (compiling).<br>
75 To do this, go to the directory, where you extracted the tarballs
76 contents and simply type <span style="font-style: italic;">make<br>
77 </span>To copy the compiled binary to your /usr/local/sbin directory
78 (installing it), type <span style="font-style: italic;">make install</span>
79 afterwards.<br>
80 <br>
81 <span style="font-style: italic;"></span><br>
82 </small></small></big></big><big style="font-weight: bold;"><big>3. How
83 to use MDK3<br>
84 </big></big><big style="font-weight: bold;"><big><br>
85 </big></big><big><big><small><small>Using MDK3 is quite simple, since
86 it comes with lots of help screens directly included in the code.<br>
87 You can easily access them by typing only <span
88 style="font-style: italic;">mdk3</span><br>
89 MDK3 displays the main help screen. To see all possible options, type <span
90 style="font-style: italic;">mdk3 --fullhelp</span><br>
91 To see only information for a specific test, type <span
92 style="font-style: italic;">mdk3 --help</span> followed by the test
93 mode identifier (b, a, p, d, m or x)<br>
94 <br>
95 Before you can use MDK3, you need to setup your wireless adaptor. As
96 far as there are different driver architectures, the way to setup your
97 adaptor may vary depending on which driver is in use. To make this
98 procedure easy, it is recommended to use airmon-ng from the aircrack
99 project, since this can setup almost every known driver correctly.<br>
100 To enable injection, your card needs to be started, switched to the
101 monitor and a bitrate and channel have to be set.<br>
102 <br>
103 This way works for most of the cards, its the generic way thats
104 provided by the kernel (sadly not every driver is using this kernel
105 interface)<br>
106 1. Insert your card, a new interface should appear (use <span
107 style="font-style: italic;">ifconfig -a</span> to show all available
108 interfaces)<br>
109 2. Start your interface with <span style="font-style: italic;">ifconfig</span>
110 [your_interface] <span style="font-style: italic;">up<br>
111 </span>3. Set the interface into monitor mode: <span
112 style="font-style: italic;">iwconfig </span>[your_interface]<span
113 style="font-style: italic;"> mode monitor</span><br>
114 4. Set channel and bitrate: <span style="font-style: italic;">iwconfig
115 </span>[your_interface] <span style="font-style: italic;">channel </span>[channel]<span
116 style="font-style: italic;"> rate 1M</span><br>
117 This sets the bitrate for your injected data to 1 MBit, the lowest
118 available rate, but with the highest possible range, to reach as many
119 clients as possible.<br>
120 IMPORTANT: You need to set the channel to the channel where the target
121 AP/client is, otherwise it won't work! This is a very common error.<br>
122 <br>
123 To find APs and clients, it is recommended to use airodump-ng. Simply
124 start it with <span style="font-style: italic;">airodump-ng</span>
125 [your_interface] first, to see the available stations. If you decided
126 on one CHANNEL where to run the test on, you should restart airodump
127 and
128 set it ONLY to this specific channel, so your card won't change
129 channels anymore to find other stations. You can do this with <span
130 style="font-style: italic;">airodump-ng -c </span>[channel]
131 [your_interface]<br>
132 The good thing of using airodump-ng is, that you don't need to care
133 about setting your card up correctly since airodump-ng already did this
134 job. Nevertheless, airmon-ng is sometimes also necessary before
135 starting airodump-ng.<br>
136 <br>
137 Your hardware is now correctly set up, and you can start usind MDK3.<br>
138 <br>
139 Another important notice for professional users: Some drivers do not
140 correctly echo back injected frames to the system, thus your injected
141 packets won't be seen if you sniff on the interface on which you are
142 injecting. To check if the frames are sent correctly you need to setup
143 another inteface on the same channel and sniff the injected frames with
144 it!<br>
145 <span style="font-style: italic;"><br>
146 <br>
147 </span></small></small></big></big><big style="font-weight: bold;"><big>4.
148 The different test modes</big></big><br>
149 <br>
150 <span style="font-weight: bold; text-decoration: underline;">b&nbsp;&nbsp;
151 - Beacon Flood Mode</span><br>
152 <br>
153 AccessPoints send out approximately 10 beacon frames per second. They
154 are to identify the network. When you scan for networks, your card does
155 in fact look for beacon frames on every available channel. With MDK3,
156 it is possible to send these beacon frames, too. So people will see
157 your fake networks when they scan with their wifi. Windows does scan
158 automatically as long as it isn't connected and shows a bubble in the
159 taskbar, if a network is found. Additionally, this mode can be used
160 to hide a network by generating thousands of fake networks with the
161 same name as the original one. This mode has several options to set
162 network name, its encryption, its speed etc. So read on to get familiar
163 with them:<br>
164 <br>
165 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -n &lt;ssid&gt;<br>
166 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This lets you set the
167 name of the network. Only networks with the given name will be faked.
168 This is used if you want to hide a network.<br>
169 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -f &lt;filename&gt;<br>
170 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This lets you read the
171 names for the networks from a file. This way you can fake multiple
172 networks at once.<br>
173 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -v &lt;filename&gt;<br>
174 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This is used to fake
175 only a very specific set of networks. Every line is this file consists
176 of the APs adress and its name. See the example file on how to use it.<br>
177 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -d<br>
178 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do not fake a real
179 network, but fake an Ad-Hoc network with clients only. (networks
180 without APs, where peers communicate directly)<br>
181 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -w<br>
182 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This generates WEP
183 encrypted networks<br>
184 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -g<br>
185 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This generates
186 networks with IEEE-802.11g 54 Mbit. Without this option, you will get
187 b-only 11 MBit networks<br>
188 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -t<br>
189 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Show networks using
190 WPA TKIP encryption<br>
191 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -a<br>
192 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Show networks using
193 WPA AES encryption<br>
194 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -m<br>
195 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Usually, MDK3
196 generates networks with a random adress. But as far as not all adresses
197 are used this day, this option refers to the adress database included
198 in MDK3 to generate only AcessPoints with adresses from known hardware
199 vendors. With this option it is hard to say, if a network is fake or
200 not.<br>
201 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -h<br>
202 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This makes MDK3 to
203 change your card's channel to the channel where the fake network should
204 actually be. Good thing about this is, its harder to determine if this
205 network is fake, since the channel given in the beacon data matches the
206 channel the packet is send on. Bad thing is, your card needs some time
207 to change on a specific channel. So this slows down the injection
208 speed. You
209 could avoid this by generating fake networks on one channel only (see
210 -c option below), but in this case, the targets don't need to change
211 their channels in order to find the correct AP, thus they find the real
212 AP a bit faster.<br>
213 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -c &lt;chan&gt;<br>
214 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the channel where
215 the fake network should be<br>
216 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -s &lt;pps&gt;<br>
217 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set speed in frames
218 per second (Default: 50). More speed = More fake networks. But don't
219 get crazy with this option. Too many frames may overflow your card's
220 buffers and it will crash!<br>
221 <br>
222 <br>
223 <span style="font-weight: bold;">EXAMPLES:</span><br>
224 <br>
225 There is a WPA TKIP network named "Hack me" on channel 11, supporting
226 up to 54 MBit with lots of clients. You want to confuse them a little
227 by generating some fake clone networks:<br>
228 <br>
229 <span style="font-style: italic;">mdk3 </span>[your_interface] <span
230 style="font-style: italic;">b -n "Hack me" -g -t -m -c 11</span><br>
231 <br>
232 The b activates beacon flood mode, -n sets the name, -g makes it 54
233 MBit, -t enables TKIP, -m makes MDK3 only use valid adresses and -c
234 sets the correct channel. Do not forget to set your card's channel
235 before your start such a test! You could also use -h option for this.<br>
236 <br>
237 <br>
238 a&nbsp;&nbsp; - Authentication DoS mode<br>
239 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sends authentication frames to all APs
240 found in range.<br>
241 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Too much clients freeze or reset some
242 APs.<br>
243 <br>
244 EXAMPLES:<br>
245 <br>
246 p&nbsp;&nbsp; - Basic probing and ESSID Bruteforce mode<br>
247 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Probes AP and check for answer, useful
248 for checking if SSID has<br>
249 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; been correctly decloaked or if AP is in
250 your adaptors sending range<br>
251 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SSID Bruteforcing is also possible with
252 this test mode.<br>
253 <br>
254 EXAMPLES:<br>
255 <br>
256 d&nbsp;&nbsp; - Deauthentication / Disassociation Amok Mode<br>
257 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Kicks everybody found from AP<br>
258 <br>
259 EXAMPLES:<br>
260 <br>
261 m&nbsp;&nbsp; - Michael shutdown exploitation (TKIP)<br>
262 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cancels all traffic continuously<br>
263 <br>
264 EXAMPLES:<br>
265 <br>
266 x&nbsp;&nbsp; - 802.1X tests<br>
267 <br>
268 EXAMPLES:<br>
269 <br>
270 <br>
271 <span style="font-weight: bold;">And for those who read this document
272 until
273 the end, here is the special Multi Destruction Mode to really
274 shutdown and destroy a network.</span><br>
275 WARNING: This could REALLY shutdown every communication, even until the
276 hardware is manually resetted. This can crash drivers, computers and
277 APs alike! So consider yourself to have been warned! Run these commands
278 only, if there is no important data transmitted and you can afford some
279 downtime!<br>
280 <br>
281 <br>
282 <br>
283 (c) Pedro Larbig 2007<br>
284 </div>
285 </div>
286 </body>
287 </html>