User Tools

Site Tools


cracking_wpa

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
cracking_wpa [2010/01/03 18:23]
netrolller3d Generalize monitor mode setup instructions for non-madwifi drivers.
cracking_wpa [2018/03/11 20:10] (current)
mister_x Removed link to trac
Line 1: Line 1:
 ====== Tutorial: How to Crack WPA/WPA2 ====== ====== Tutorial: How to Crack WPA/WPA2 ======
-Version: 1.18 September 252009\\+Version: 1.20 March 072010\\
 By: darkAudax By: darkAudax
  
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://​trac.aircrack-ng.org/​wiki/​Team|Aircrack-ng team]] for producing such a great robust tool.  
  
 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:
    ​ath0 ​           Atheros ​        ​madwifi-ng VAP (parent: wifi0)    ​ath0 ​           Atheros ​        ​madwifi-ng VAP (parent: wifi0)
  
-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 "​madwifi-ng"​ as the driver - follow the madwifi-ng-specific steps to set up the Atheros card. Both entries of the Atheros card show "​madwifi-ng"​ as the driver - follow the madwifi-ng-specific steps to set up the Atheros card.
 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/​docs/​wireless/​technology/​channel/​deployment/​guide/Channel.html#​wp134132 ​.  This will give you the frequency for each channel.
-http://www.rflinx.com/help/calculations/#​2.4ghz_wifi_channels then select the "​Wifi ​Channel ​Selection and Channel Overlap"​ tab.  This will give you the frequency for each channel.+
  
 === 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:​14:​6C:​7E:​40:​80"​ in the top right-hand corner. ​ This means a four-way handshake was successfully captured. ​ See just above for an example screenshot. To see if you captured any handshake packets, there are two ways.  Watch the airodump-ng screen for " WPA handshake: 00:​14:​6C:​7E:​40:​80"​ in the top right-hand corner. ​ This means a four-way handshake was successfully captured. ​ See just above for an example screenshot.
  
-use Wireshark and apply a filter of "​eapol"​. ​ This displays only eapol packets you are interested in.  Thus you can see if capture contains 0,1,2,3 or 4 eapol packets.+Use Wireshark and apply a filter of "​eapol"​. ​ This displays only eapol packets you are interested in.  Thus you can see if capture contains 0,1,2,3 or 4 eapol packets.
  
  
 ==== Step 3 - Use aireplay-ng to deauthenticate the wireless client ==== ==== Step 3 - Use aireplay-ng to deauthenticate the wireless client ====
  
-This step is optional. ​ You only perform this step if you opted to actively speed up the process. ​ The other constraint is that there must be a wireless client currently associated with the AP.  If there is no wireless client currently associated with the AP, then move onto the next step and be patient. ​ Needless to say, if a wireless client shows up later, you can backtrack and perform this step.+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. ​ The other constraint is that there must be a wireless client currently associated with the AP.  If there is no wireless client currently associated with the AP, then you have to be patient ​and wait for one to connect to the AP so that a handshake can be captured.  Needless to say, if a wireless client shows up later and airodump-ng did not capture the handshake, you can backtrack and perform this step.
  
 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 is what we use to break the WPA/WPA2 pre-shared key. 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 is what we use to break the WPA/WPA2 pre-shared key.
cracking_wpa.1262539432.txt.gz · Last modified: 2010/01/03 18:23 by netrolller3d