cracking_wpa
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
cracking_wpa [2009/09/25 21:20] – Clarified that the passphrase must be in the dictionary in order to break wpa/wpa2 darkaudax | cracking_wpa [2018/03/11 20:10] – Removed link to trac mister_x | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Tutorial: How to Crack WPA/WPA2 ====== | ====== Tutorial: How to Crack WPA/WPA2 ====== | ||
- | Version: 1.18 September 25, 2009\\ | + | Version: 1.20 March 07, 2010\\ |
By: darkAudax | By: darkAudax | ||
Line 16: | Line 16: | ||
The impact of having to use a brute force approach is substantial. | The impact of having to use a brute force approach is substantial. | ||
- | **IMPORTANT** This means that that the passphrase must be contained in the dictionary you are using to break WPA/ | + | **IMPORTANT** This means that the passphrase must be contained in the dictionary you are using to break WPA/ |
There is no difference between cracking WPA or WPA2 networks. | There is no difference between cracking WPA or WPA2 networks. | ||
It is recommended that you experiment with your home wireless access point to get familiar with these ideas and techniques. If you do not own a particular access point, please remember to get permission from the owner prior to playing with it. | It is recommended that you experiment with your home wireless access point to get familiar with these ideas and techniques. If you do not own a particular access point, please remember to get permission from the owner prior to playing with it. | ||
- | |||
- | I would like to acknowledge and thank the [[http:// | ||
Please send me any constructive feedback, positive or negative. Additional troubleshooting ideas and tips are especially welcome. | Please send me any constructive feedback, positive or negative. Additional troubleshooting ideas and tips are especially welcome. | ||
Line 37: | Line 35: | ||
===== Equipment used ===== | ===== Equipment used ===== | ||
- | |||
- | To follow this tutorial at home, you must have two wireless cards. | ||
In this tutorial, here is what was used: | In this tutorial, here is what was used: | ||
Line 69: | Line 65: | ||
==== Step 1 - Start the wireless interface in monitor mode ==== | ==== Step 1 - Start the wireless interface in monitor mode ==== | ||
- | The purpose of this step is to put your card into what is called monitor mode. Monitor mode is the mode whereby your card can listen to every packet in the air. Normally your card will only " | + | The purpose of this step is to put your card into what is called monitor mode. Monitor mode is the mode whereby your card can listen to every packet in the air. Normally your card will only " |
+ | |||
+ | The exact procedure for enabling monitor mode varies depending on the driver you are using. To determine the driver (and the correct procedure | ||
+ | |||
+ | | ||
+ | |||
+ | On a machine with a Ralink, an Atheros and a Broadcom wireless card installed, the system responds: | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | The presence of a [phy0] tag at the end of the driver name is an indicator | ||
+ | Both entries of the Atheros card show "madwifi-ng" | ||
+ | Finally, the Ralink shows neither of these indicators, so it is using an ieee80211 driver - see the generic instructions for setting it up. | ||
+ | |||
+ | === Step 1a - Setting up madwifi-ng === | ||
Line 130: | Line 145: | ||
In the response above, you can see that ath0 is in monitor mode, on the 2.452GHz frequency which is channel 9 and the Access Point shows the MAC address of your wireless card. Only the madwifi-ng drivers show the card MAC address in the AP field, other drivers do not. So everything is good. It is important to confirm all this information prior to proceeding, otherwise the following steps will not work properly. | In the response above, you can see that ath0 is in monitor mode, on the 2.452GHz frequency which is channel 9 and the Access Point shows the MAC address of your wireless card. Only the madwifi-ng drivers show the card MAC address in the AP field, other drivers do not. So everything is good. It is important to confirm all this information prior to proceeding, otherwise the following steps will not work properly. | ||
- | To match the frequency to the channel, check out: | + | To match the frequency to the channel, check out: http://www.cisco.com/en/US/ |
- | http://www.rflinx.com/help/calculations/# | + | |
+ | === Step 1b - Setting up mac80211 drivers === | ||
+ | |||
+ | Unlike madwifi-ng, you do not need to remove the wlan0 interface when setting up mac80211 drivers. Instead, use the following command to set up your card in monitor mode on channel 9: | ||
+ | |||
+ | | ||
+ | |||
+ | The system responds: | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | |||
+ | Notice that airmon-ng enabled monitor-mode //on mon0//. So, the correct interface name to use in later parts of the tutorial is mon0. Wlan0 is still in regular (managed) mode, and can be used as usual, provided that the AP that wlan0 is connected to is on the same channel as the AP you are attacking, and you are not performing any channel-hopping. | ||
+ | |||
+ | To confirm successful setup, run " | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | Retry min limit: | ||
+ | | ||
+ | Power Management: | ||
+ | Link Quality: | ||
+ | Rx invalid nwid: | ||
+ | Tx excessive retries: | ||
+ | |||
+ | | ||
+ | Retry min limit: | ||
+ | | ||
+ | Power Management: | ||
+ | Link Quality: | ||
+ | Rx invalid nwid: | ||
+ | Tx excessive retries: | ||
+ | |||
+ | |||
+ | Here, mon0 is seen as being in monitor mode, on channel 9 (2.452GHz). Unlike madwifi-ng, the monitor interface has no Access Point field at all. Also notice that wlan0 is still present, and in managed mode - this is normal. Because both interfaces share a common radio, they must always be tuned to the same channel - changing the channel on one interface also changes channel on the other one. | ||
+ | |||
+ | === Step 1c - Setting up other drivers === | ||
+ | |||
+ | For other (ieee80211-based) drivers, simply run the following command to enable monitor mode (replace rausb0 with your interface name): | ||
+ | |||
+ | | ||
+ | |||
+ | The system responds: | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | At this point, the interface should be ready to use. | ||
==== Step 2 - Start airodump-ng to collect authentication handshake ==== | ==== Step 2 - Start airodump-ng to collect authentication handshake ==== | ||
Line 181: | Line 252: | ||
To see if you captured any handshake packets, there are two ways. Watch the airodump-ng screen for " WPA handshake: 00: | To see if you captured any handshake packets, there are two ways. Watch the airodump-ng screen for " WPA handshake: 00: | ||
- | use Wireshark and apply a filter of " | + | Use Wireshark and apply a filter of " |
==== Step 3 - Use aireplay-ng to deauthenticate the wireless client ==== | ==== Step 3 - Use aireplay-ng to deauthenticate the wireless client ==== | ||
- | This step is optional. | + | This step is optional. If you are patient, you can wait until airodump-ng captures a handshake when one or more clients connect to the AP. You only perform this step if you opted to actively speed up the process. |
This step sends a message to the wireless client saying that that it is no longer associated with the AP. The wireless client will then hopefully reauthenticate with the AP. The reauthentication is what generates the 4-way authentication handshake we are interested in collecting. | This step sends a message to the wireless client saying that that it is no longer associated with the AP. The wireless client will then hopefully reauthenticate with the AP. The reauthentication is what generates the 4-way authentication handshake we are interested in collecting. |
cracking_wpa.txt · Last modified: 2022/01/02 21:34 by mister_x