cracking_wpa
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cracking_wpa [2010/01/03 18:23] – Generalize monitor mode setup instructions for non-madwifi drivers. netrolller3d | cracking_wpa [2022/01/02 21:34] (current) – Fixed dead links 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 | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | This tutorial walks you through cracking WPA/WPA2 networks which use pre-shared keys. I recommend you do some background reading to better understand what WPA/WPA2 is. The [[http:// | + | This tutorial walks you through cracking WPA/WPA2 networks which use pre-shared keys. I recommend you do some background reading to better understand what WPA/WPA2 is. The [[http:// |
WPA/WPA2 supports many types of authentication beyond pre-shared keys. [[aircrack-ng]] can ONLY crack pre-shared keys. So make sure [[airodump-ng]] shows the network as having the authentication type of PSK, otherwise, don't bother trying to crack it. | WPA/WPA2 supports many types of authentication beyond pre-shared keys. [[aircrack-ng]] can ONLY crack pre-shared keys. So make sure [[airodump-ng]] shows the network as having the authentication type of PSK, otherwise, don't bother trying to crack it. | ||
Line 21: | Line 21: | ||
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 84: | Line 80: | ||
| | ||
- | The presence of a [phy0] tag at the end of the driver name is an indicator for mac80211, so the Broadcom card is using a mac80211 driver. **Note that mac80211 is supported only since aircrack-ng v1.0-rc1, and it won't work with v0.9.1, which this tutorial primarily refers to.** | + | The presence of a [phy0] tag at the end of the driver name is an indicator for mac80211, so the Broadcom card is using a mac80211 driver. **Note that mac80211 is supported only since aircrack-ng v1.0-rc1, and it won't work with v0.9.1.** |
Both entries of the Atheros card show " | Both entries of the Atheros card show " | ||
Finally, the Ralink shows neither of these indicators, so it is using an ieee80211 driver - see the generic instructions for setting it up. | Finally, the Ralink shows neither of these indicators, so it is using an ieee80211 driver - see the generic instructions for setting it up. | ||
Line 149: | 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 === | === Step 1b - Setting up mac80211 drivers === | ||
Line 257: | 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.1262539432.txt.gz · Last modified: 2010/01/03 18:23 by netrolller3d