newbie_guide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
newbie_guide [2007/04/02 19:58] – add instructions for double dashes in commands darkaudax | newbie_guide [2018/10/08 04:09] – Updated links mister_x | ||
---|---|---|---|
Line 2: | Line 2: | ||
Idea and initial work: ASPj\\ | Idea and initial work: ASPj\\ | ||
Additions by: a number of good souls\\ | Additions by: a number of good souls\\ | ||
- | Last updated: | + | Last updated: |
\\ | \\ | ||
- | This tutorial will give you the basics to get started using the aircrack-ng suite. | + | This tutorial will give you the basics to get started using the aircrack-ng suite. |
Although it does not cover all the steps from start to finish like this tutorial, the [[simple_wep_crack|Simple WEP Crack]] tutorial covers the actual aircrack-ng steps in much more detail. | Although it does not cover all the steps from start to finish like this tutorial, the [[simple_wep_crack|Simple WEP Crack]] tutorial covers the actual aircrack-ng steps in much more detail. | ||
- | In the examples, the option " | ||
====== Setting up Hardware, Installing Aircrack-ng ====== | ====== Setting up Hardware, Installing Aircrack-ng ====== | ||
Line 16: | Line 15: | ||
Needless to say, you need a wireless card which is compatible with the aircrack-ng suite. | Needless to say, you need a wireless card which is compatible with the aircrack-ng suite. | ||
- | To determine to which category your card belongs to, see [[compatibility_drivers|hardware compatibility page]]. Read [[http:// | + | To determine to which category your card belongs to, see [[compatibility_drivers|hardware compatibility page]]. Read [[compatible_cards|Tutorial: |
- | First, you need to know which chipset is used in your wireless card and which driver you need for it. You will have determined this using the information in the previous paragraph. | + | First, you need to know which chipset is used in your wireless card and which driver you need for it. You will have determined this using the information in the previous paragraph. |
As I own a Ralink USB device, I am providing the steps to get it working with Aircrack-ng. | As I own a Ralink USB device, I am providing the steps to get it working with Aircrack-ng. | ||
Line 27: | Line 26: | ||
===== RaLink USB rt2570 Setup guide ===== | ===== RaLink USB rt2570 Setup guide ===== | ||
- | If you own a rt2570 USB device (like D-Link DWL-G122 rev. B1 or Linksys WUSB54G v4) you should use the drivers from http:// | + | If you own a rt2570 USB device (like D-Link DWL-G122 rev. B1 or Linksys WUSB54G v4) you should use the drivers from [[https:// |
Lets unpack, compile and install the drivers: | Lets unpack, compile and install the drivers: | ||
Line 46: | Line 45: | ||
==== Source ==== | ==== Source ==== | ||
- | Get the latest copy of aircrack-ng from the homepage: http://www.aircrack-ng.org | + | Get the latest copy of aircrack-ng from the [[main|homepage]]. |
The following commands would have to be changed if you use a newer version of the software. | The following commands would have to be changed if you use a newer version of the software. | ||
Unpacking, compiling, installing: | Unpacking, compiling, installing: | ||
- | tar xfz aircrack-ng-0.7.tar.gz | + | tar xfz aircrack-ng-1.4.tar.gz |
- | cd aircrack-ng-0.7 | + | cd aircrack-ng-1.4 |
+ | autoreconf -i | ||
+ | ./configure --with-experimental | ||
make | make | ||
make install | make install | ||
- | As usual, the last step needs to be performed as root, use **su** to login as root (use **sudo make** install for Ubuntu). | + | As usual, the last step needs to be performed as root, use **su** or **sudo -s** to login as root (use **sudo make** install for Ubuntu). |
==== YUM ==== | ==== YUM ==== | ||
+ | |||
+ | **WARNING!!!** Currently, neither of the repositories hosts the latest version of Aircrack-ng. It's recommended that you use the first method instead. | ||
If you are using a system like Redhat Linux or Fedora Core you can install aircrack-ng with yum. First you have to add the repository of [[http:// | If you are using a system like Redhat Linux or Fedora Core you can install aircrack-ng with yum. First you have to add the repository of [[http:// | ||
Line 66: | Line 69: | ||
==== RPM ==== | ==== RPM ==== | ||
+ | |||
+ | **WARNING!!!** Currently, neither of the repositories hosts the latest version of Aircrack-ng. It's recommended that you use the first method instead. | ||
If you are using a system which is rpm-based then you can take the easy way to install aircrack-ng. (Example for Redhat Linux 4) | If you are using a system which is rpm-based then you can take the easy way to install aircrack-ng. (Example for Redhat Linux 4) | ||
Line 106: | Line 111: | ||
* WPA/WPA2 is in use, you need EAPOL authentication. The AP will deny you at step 2. | * WPA/WPA2 is in use, you need EAPOL authentication. The AP will deny you at step 2. | ||
* Access Point has a list of allowed clients (MAC addresses), and it lets no one else connect. This is called MAC filtering. | * Access Point has a list of allowed clients (MAC addresses), and it lets no one else connect. This is called MAC filtering. | ||
- | * Access Point uses Shared Key Authentication, | + | * Access Point uses Shared Key Authentication, |
====== Simple sniffing and cracking ====== | ====== Simple sniffing and cracking ====== | ||
+ | |||
Line 122: | Line 128: | ||
[[airmon-ng]] start rausb0 | [[airmon-ng]] start rausb0 | ||
- | To confirm it is in monitor mode, run "iwlist" and confirm the mode. The [[airmon-ng|airmon-ng page]] on the Wiki has generic information and how to start it for other drivers. | + | To confirm it is in monitor mode, run "iwconfig" and confirm the mode. The [[airmon-ng|airmon-ng page]] on the Wiki has generic information and how to start it for other drivers. |
Then, start airodump-ng to look out for networks: | Then, start airodump-ng to look out for networks: | ||
Line 129: | Line 135: | ||
" | " | ||
- | Take a look in the documentation of the nic driver. | + | Take a look in the documentation of the nic driver. For most newer drivers, the primary interface name is " |
If airodump-ng could connect to the WLAN device, you'll see a screen like this: | If airodump-ng could connect to the WLAN device, you'll see a screen like this: | ||
- | {{http:// | + | {{https:// |
[[airodump-ng]] hops from channel to channel and shows all access points it can receive beacons from. Channels 1 to 14 are used for 802.11b and g (in US, they only are allowed to use 1 to 11; 1 to 13 in Europe with some special cases; 1-14 in Japan). Channels between 36 and 149 are used for 802.11a. The current channel is shown in the top left corner. | [[airodump-ng]] hops from channel to channel and shows all access points it can receive beacons from. Channels 1 to 14 are used for 802.11b and g (in US, they only are allowed to use 1 to 11; 1 to 13 in Europe with some special cases; 1-14 in Japan). Channels between 36 and 149 are used for 802.11a. The current channel is shown in the top left corner. | ||
Line 144: | Line 150: | ||
^ PWR | Signal strength. Some drivers don't report it | | ^ PWR | Signal strength. Some drivers don't report it | | ||
^ Beacons | ^ Beacons | ||
- | ^ Data | Number of data frames | + | ^ Data | Number of data frames |
^ CH | Channel the AP is operating on | | ^ CH | Channel the AP is operating on | | ||
^ MB | Speed or AP Mode. 11 is pure 802.11b, 54 pure 802.11g. Values between are a mixture | ^ MB | Speed or AP Mode. 11 is pure 802.11b, 54 pure 802.11g. Values between are a mixture | ||
Line 155: | Line 161: | ||
^ STATION | ^ STATION | ||
^ PWR | Signal strength. Some drivers don't report it | | ^ PWR | Signal strength. Some drivers don't report it | | ||
- | ^ Packets | + | ^ Packets |
^ Probes | ^ Probes | ||
- | Now you should look out for a target network. It should have a client connected because cracking networks without a client is an advanced topic (See [[http:// | + | Now you should look out for a target network. It should have a client connected because cracking networks without a client is an advanced topic (See [[how_to_crack_wep_with_no_clients|How to crack wep with no clients]]). It should use WEP encryption and have a high signal strength. Maybe you can re-position your antenna to get a better signal. Often a few centimeters make a big difference in signal strength. |
In the example above the net 00: | In the example above the net 00: | ||
Line 166: | Line 172: | ||
Because of the channel hopping you won't capture all packets from your target net. So we want to listen just on one channel and additionally write all data to disk to be able to use it for cracking: | Because of the channel hopping you won't capture all packets from your target net. So we want to listen just on one channel and additionally write all data to disk to be able to use it for cracking: | ||
- | airodump-ng -c 11 - -bssid 00: | + | airodump-ng -c 11 --bssid 00: |
- | With the -c parameter you tune to a channel and the parameter after -w is the prefix to the network dumps written to disk. The "- -bssid" | + | With the -c parameter you tune to a channel and the parameter after -w is the prefix to the network dumps written to disk. The "-'''' |
- | You can also add the - -ivs parameter. This tells [[airodump-ng]] to only capture | + | Before being able to crack WEP you'll usually need between 40 000 and 85 000 different Initialization Vectors (IVs). Every data packet contains an IV. IVs can be re-used, so the number of different |
- | Before being able to crack WEP you'll usually need between 250.000 and 500.000 different Initialization Vectors (IVs). Every data packet contains an IV. IVs can be re-used, so the number of different IVs is usually a bit lower than the number of data packets captured. | + | So you'll have to wait and capture |
- | + | ||
- | So you'll have to wait and capture | + | |
===== Cracking ===== | ===== Cracking ===== | ||
Line 186: | Line 190: | ||
For more information about [[aircrack-ng]] parameters, description of the output and usage see the [[aircrack-ng|manual]]. | For more information about [[aircrack-ng]] parameters, description of the output and usage see the [[aircrack-ng|manual]]. | ||
- | The number of IVs you need to crack a key is not fixed. This is because some IVs are weaker and leak more information about the key than others. Usually these weak IVs are randomly mixed in between the stonger | + | The number of IVs you need to crack a key is not fixed. This is because some IVs are weaker and leak more information about the key than others. Usually these weak IVs are randomly mixed in between the stronger |
- | There are some more advanced APs out there that use an algorithm to filter out weak IVs. The result is either that you can't get more than " | + | There are some more advanced APs out there that use an algorithm to filter out weak IVs. The result is either that you can't get more than " |
====== Active attacks ====== | ====== Active attacks ====== | ||
- | |||
===== Injection support ===== | ===== Injection support ===== | ||
- | Most devices don't support injection - at least not without patched drivers. Take a look at the [[compatibility_drivers|compatibility page]], column aireplay. | + | Most devices don't support injection - at least not without patched drivers. Some only support certain attacks. Take a look at the [[compatibility_drivers|compatibility page]], column aireplay. |
- | The first step is to make sure packet injection really works with your card and driver. The easiest way to test it is the [[fake authentication]] attack. | + | The first step is to make sure packet injection really works with your card and driver. The easiest way to test it is the [[injection_test|injection test]] attack. Make sure to perform this test prior to proceeding. |
You'll need the BSSID (AP MAC) and ESSID (network name) of an AP that does not do MAC filtering (e.g. your own) and must be in range of the AP. | You'll need the BSSID (AP MAC) and ESSID (network name) of an AP that does not do MAC filtering (e.g. your own) and must be in range of the AP. | ||
- | The first thing to do is find out the MAC of your own WLAN device. Sometimes there is a label with the MAC on the device. But you can always find | + | Try to connect |
- | it out using the ifconfig command (the 6 Hex bytes after " | + | |
- | Then you can try to connect to your AP using [[aireplay-ng]]: | + | |
- | aireplay-ng - -fakeauth 0 -e "your network ESSID" -a 00: | + | The value after -a is the BSSID of your AP. |
- | + | ||
- | The value after -a is the BSSID of your AP, the value after -h is the MAC of your own WLAN device. | + | |
If injection works you should see something like this: | If injection works you should see something like this: | ||
Line 216: | Line 216: | ||
If not | If not | ||
- | - double-check ESSID, BSSID and your own MAC | + | - double-check ESSID and BSSID |
- make sure your AP has MAC filtering disabled | - make sure your AP has MAC filtering disabled | ||
- test it against another AP | - test it against another AP | ||
Line 228: | Line 228: | ||
==== The idea ==== | ==== The idea ==== | ||
- | [[http:// | + | [[https:// |
sends back an answer. Because WEP does not protect against replay, you can sniff a packet, send it out again and again and it is still valid. | sends back an answer. Because WEP does not protect against replay, you can sniff a packet, send it out again and again and it is still valid. | ||
So you just have to capture and replay an ARP-request targeted at the AP to create lots of traffic (and sniff IVs). | So you just have to capture and replay an ARP-request targeted at the AP to create lots of traffic (and sniff IVs). | ||
+ | |||
==== The lazy way ==== | ==== The lazy way ==== | ||
Line 237: | Line 238: | ||
Wait for a client to show up on the target network. Then start the attack: | Wait for a client to show up on the target network. Then start the attack: | ||
- | aireplay-ng - -arpreplay -b 00: | + | aireplay-ng --arpreplay -b 00: |
-b specifies the target BSSID, -h the MAC of the connected client. | -b specifies the target BSSID, -h the MAC of the connected client. | ||
Line 243: | Line 244: | ||
Now you have to wait for an ARP packet to arrive. Usually you'll have to wait for a few minutes (or look at the next chapter). | Now you have to wait for an ARP packet to arrive. Usually you'll have to wait for a few minutes (or look at the next chapter). | ||
- | If you were successfull, you'll see something like this: | + | If you were successful, you'll see something like this: |
Saving ARP requests in replay_arp-0627-121526.cap | Saving ARP requests in replay_arp-0627-121526.cap | ||
Line 252: | Line 253: | ||
the -r < | the -r < | ||
- | If the number of data packets received by airodump-ng sometimes stops increasing you maybe have to reduce the replay-rate. You do this with the -x <packets per second> option. I usually start out with 50 and reduce until packets are received | + | When using the arp injection technique, you can use the PTW method to crack the WEP key. This dramatically reduces the number of data packets you need and also the time needed. |
+ | |||
+ | If the number of data packets received by airodump-ng sometimes stops increasing you maybe have to reduce the replay-rate. You do this with the -x <packets per second> option. I usually start out with 50 and reduce until packets are received | ||
==== The aggressive way ==== | ==== The aggressive way ==== | ||
- | Most operating | + | Most operating |
Keep your airodump-ng and aireplay-ng running. Open another window and run a [[deauthentication]] attack: | Keep your airodump-ng and aireplay-ng running. Open another window and run a [[deauthentication]] attack: | ||
- | aireplay-ng - -deauth 5 -a 00: | + | aireplay-ng --deauth 5 -a 00: |
-a is the BSSID of the AP, -c the MAC of the targeted client. | -a is the BSSID of the AP, -c the MAC of the targeted client. | ||
Line 272: | Line 275: | ||
====== Further tools and information ====== | ====== Further tools and information ====== | ||
- | [[http:// | + | [[https:// |
newbie_guide.txt · Last modified: 2018/11/21 23:31 by mister_x