User Tools

Site Tools


fake_authentication

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
fake_authentication [2007/04/14 12:16]
raimund
fake_authentication [2010/11/21 13:18]
sleek typos
Line 4: Line 4:
 ===== Description ===== ===== Description =====
  
-The fake authentication attack allows you to perform the two types of WEP authentication (Open System and Shared Key) plus associate with the access point (AP).  This is useful ​is only useful when you need an associated MAC address in various [[aireplay-ng]] attacks and there is currently no associated client. ​ It should be noted that the fake authentication attack does NOT generate any ARP packets.+The fake authentication attack allows you to perform the two types of WEP authentication (Open System and Shared Key) plus associate with the access point (AP).  This is only useful when you need an associated MAC address in various [[aireplay-ng]] attacks and there is currently no associated client. ​ It should be noted that the fake authentication attack does NOT generate any ARP packets.  Fake authentication cannot be used to authenticate/​associate with WPA/WPA2 Access Points.
  
 ===== Usage ===== ===== Usage =====
Line 15: Line 15:
   *-e teddy is the wireless network name   *-e teddy is the wireless network name
   *-a 00:​14:​6C:​7E:​40:​80 is the access point MAC address   *-a 00:​14:​6C:​7E:​40:​80 is the access point MAC address
-  *-h 00:​09:​5B:​EC:​EE:​F2 is our card MAC addresss+  *-h 00:​09:​5B:​EC:​EE:​F2 is our card MAC address
   *-y sharedkeyxor is the name of file containing the PRGA xor bits.  This is only used for shared key authentication. ​ Open system authentication,​ which is typical, does not require this.   *-y sharedkeyxor is the name of file containing the PRGA xor bits.  This is only used for shared key authentication. ​ Open system authentication,​ which is typical, does not require this.
   *ath0 is the wireless interface name   *ath0 is the wireless interface name
Line 43: Line 43:
   *-e teddy is the wireless network name   *-e teddy is the wireless network name
   *-a 00:​14:​6C:​7E:​40:​80 is the access point MAC address   *-a 00:​14:​6C:​7E:​40:​80 is the access point MAC address
-  *-h 00:​09:​5B:​EC:​EE:​F2 is our card MAC addresss+  *-h 00:​09:​5B:​EC:​EE:​F2 is our card MAC address
   *ath0 is the wireless interface name   *ath0 is the wireless interface name
  
Line 70: Line 70:
   # and so on.   # and so on.
  
-Here is an example of a shared key authentication. ​ It does assume you have a PRGA xor file.  See the [[http://​aircrack-ng.org/​doku.php?​id=shared_key|How to do shared key fake authentication]] tutorial for more details.+Here is an example of a shared key authentication. ​ It does assume you have a PRGA xor file.  See the [[shared_key|How to do shared key fake authentication]] tutorial for more details.
  
    ​aireplay-ng -1 0  -e teddy -y sharedkey-04-00-14-6C-7E-40-80.xor -a 00:​14:​6C:​7E:​40:​80 -h 00:​09:​5B:​EC:​EE:​F2 ath0    ​aireplay-ng -1 0  -e teddy -y sharedkey-04-00-14-6C-7E-40-80.xor -a 00:​14:​6C:​7E:​40:​80 -h 00:​09:​5B:​EC:​EE:​F2 ath0
Line 76: Line 76:
 Where: Where:
   * -1 means fake authentication   * -1 means fake authentication
-  * 0 means only athenticate ​once+  * 0 means only authenticate ​once
   * -e teddy is the SSID of the network   * -e teddy is the SSID of the network
   * -y sharedkey-04-00-14-6C-7E-40-80.xor is the name of file containing the PRGA xor bits   * -y sharedkey-04-00-14-6C-7E-40-80.xor is the name of file containing the PRGA xor bits
Line 95: Line 95:
  
 ===== Usage Tips ===== ===== Usage Tips =====
- 
- 
 ==== Setting MAC address ==== ==== Setting MAC address ====
  
-It is good practice to set your card's MAC address to the one you specify via the "​-h"​ parameter if they are different. ​ Having them the same, ensures that wireless "​ACK"​s are sent by your card.  This means subsequent attacks work smoothly. ​+It is good practice to set your card's MAC address to the one you specify via the "​-h"​ parameter if they are different. Having them the same, ensures that wireless "​ACK"​s are sent by your card. This means subsequent attacks work smoothly. ​
  
-Detailed instructions on changing the card MAC address can be found in the FAQ: [[http://​aircrack-ng.org/​doku.php?​id=faq#​how_do_i_change_my_card_s_mac_address|How do I change my card's MAC address ?]].+Detailed instructions on changing the card MAC address can be found in the FAQ: [[faq#​how_do_i_change_my_card_s_mac_address|How do I change my card's MAC address ?]].
  
-Troubleshooting Tip: A normal MAC address looks like this: 00:​09:​5B:​EC:​EE:​F2. The first half (00:09:5B) of each MAC address is the manufacturer. The second half (EC:EE:F2) is unique to each network card. Many access points will ignore ​invalid ​MAC addresses. So make sure to use a valid wireless card manufacturer ​code when you make up MAC addresses. Otherwise your packets may be ignored.+Troubleshooting Tip: A normal MAC address looks like this: 00:​09:​5B:​EC:​EE:​F2. ​ It is composed of six octets.  ​The first half (00:09:5B) of each MAC address is known as the Organizationally Unique Identifier (OUI). ​ Simply put, it is the card manufacturer. The second half (EC:​EE:​F2) ​is known as the extension identifier and is unique to each network card within the specific OUI. Many access points will ignore MAC addresses ​with invalid OUIs. So make sure you use a valid OUI code code when you make up MAC addresses. Otherwiseyour packets may be ignored ​by the Access Point. ​ The current list of OUIs may be found [[http://​standards.ieee.org/​regauth/​oui/​oui.txt|here]].
  
 ==== Injecting in Managed Mode ==== ==== Injecting in Managed Mode ====
Line 126: Line 124:
 ==== Examples of successful authentications ==== ==== Examples of successful authentications ====
  
-When toubleshooting ​failed fake authentications,​ it can be helpful to do a packet capture and compare it to successful ones.  As well, simply reviewing this packet captures with WireShark can be very educational.+When troubleshooting ​failed fake authentications,​ it can be helpful to do a packet capture and compare it to successful ones.  As well, simply reviewing this packet captures with WireShark can be very educational.
  
 Here are packet captures of the two types of authentication - open and shared key: Here are packet captures of the two types of authentication - open and shared key:
Line 180: Line 178:
    ​Please specify a PRGA-file (-y).    ​Please specify a PRGA-file (-y).
  
-See the [[http://​aircrack-ng.org/​doku.php?​id=shared_key|How to do shared key fake authentication]] tutorial.+See the [[shared_key|How to do shared key fake authentication]] tutorial.
  
-==== Other problems and solutions ==== 
  
-If fake authentication is never successful (aireplay-ng keeps sending authentication requests) then MAC address filtering may be in place. ​ This is where the access ​point will only accept connections from specific MAC addresses. ​ In this case you will need to obtain a valid MAC address by observation using [[airodump-ng]]. ​ Do not do a fake authentication for a specific MAC address if the client is active ​on the AP.+==== MAC access ​controls enabled ​on the AP ====
  
-Sometimeswhen you try to fakeauth ​open networks ​(no encryption), it fails to associate ​(code 12).+If fake authentication is never successful (aireplay-ng keeps sending authentication requests) then MAC address filtering may be in place. ​ This is where the access point will only accept connections from specific MAC addresses. ​ In this case you will need to obtain a valid MAC address by observation using [[airodump-ng]]. ​ Do not do a fake authentication for a specific MAC address if the client is active on the AP.  See the MAC access control troubleshooting tip [[i_am_injecting_but_the_ivs_don_t_increase#​troubleshooting_tips|here]] 
 + 
 + 
 +==== Waiting for beacon frame ==== 
 +When you enter the commandthe system freezes or a line is printed with "​Waiting for beacon frame" and then no further activity occurs. 
 + 
 +There are many possible root causes of this problem: 
 + 
 +  * The wireless card is set to a channel which is different then the AP.  Solution: Use iwconfig and confirm the card is set to the same channel as the AP. 
 +  * The card is scanning channels. ​ Solution: Start airodump-ng with the "​-c"​ or "​--channel"​ parameter and set it to the same channel as the AP. 
 +  * The ESSID is wrong. ​ Solution: Enter the correct value. ​ If if contains spaces or special characters then enclose it in quotes. ​ For the complete details, see this [[faq#​how_to_use_spaces_double_quote_and_single_quote_in_ap_names|FAQ entry]]. 
 +  * The BSSID is wrong. ​ Solution: Enter the correct value. 
 +  * You are too far away from the AP and are not receiving any beacons. ​ Solution: ​ You can use tcpdump and/or airodump-ng to confirm ​you are in fact receiving beacons for the AP.  If not, move closer. 
 +  * You are not receiving beacons for the AP:  Solution: ​ Use "​tcpdump -n -vvv -e -s0 -i <​interface name>" ​to confirm you are receiving beacons. ​ Assuming you have dealt with with potential problems above, it could be the drivers or you have not put the card into monitor mode. 
 + 
 +For all of the above, running airodump-ng and the related text file should provide all the information you require identify and correct the problem. 
 + 
 + 
 +==== Airodump-ng does not show the ESSID ==== 
 + 
 +Airodump-ng does not show the ESSID! ​ How do I do fake authentication since this is a required parameter?​ 
 + 
 +Answer: ​ You need to patient. ​ When a client associates with the AP, then airodump-ng will obtain and display the ESSID. ​ If you are impatient then [[deauthentication|deauthenticate a client]] to get the  ESSID immediately. 
 + 
 + 
 +==== Error Message "​Denied (Code 1) is WPA in use?" ==== 
 + 
 +You get something similar to this: 
 + 
 +   ​Sending Authentication Request 
 +   ​Authentication successful 
 +   ​Sending Association Request 
 +   ​Association successful 
 +   ​Denied (Code 1) is WPA in use? 
 + 
 +You cannot use fake authentication with a WPA/WPA Access Point. ​ It may only be used with WEP Access Points. 
 + 
 + 
 +==== Error Message "​Denied (code 10), open (no WEP)?" ==== 
 + 
 +You cannot use fake authentication with an Open AP.  Open meaning there is no WEP encryption enabled. ​ There is no WEP key to crack! 
 + 
 + 
 +==== Error Message "​Denied ​(code 12), wrong ESSID or WPA?" ==== 
 + 
 +First, ensure the AP you are trying to connect to is WEP.  You cannot do fake authentication to a WPA/WPA2 network. 
 + 
 +The most likely reason to get this error message is when the ESSID specified with "​-e"​ does not EXACTLY match the real ESSID. ​ Capitalization,​ spaces, special characters and so on must match exactly. ​ See this FAQ entry [[faq#​how_to_use_spaces_double_quote_and_single_quote_etc._in_ap_names|FAQ entry]] for instructions on how to handle unusual ESSIDs.  
 + 
 + 
 +==== Error message "code (XX)" ==== 
 +You receive an error messages referencing a code number. ​ This [[http://​download.aircrack-ng.org/​wiki-files/​other/​managementframes.pdf|Management Frames description]] is an excellent description of the various error codes you may receive. ​ Just look for the number relating to the authentication or association phase when you received the error. 
 + 
 + 
 +==== Other problems and solutions ====
  
 Also make sure that: Also make sure that:
  
-  * You are physically close enough to the access point.+  * You are physically close enough to the access point.  You can confirm that you can communicate with the specific AP by following [[injection_test#​hidden_or_specific_ssid|these instructions]].
   * Make sure you are using a real MAC address (see discussion above)   * Make sure you are using a real MAC address (see discussion above)
-  * The wireless card driver is properly patched and installed. +  * The wireless card driver is properly patched and installed.  Use the [[injection_test|injection test]] to confirm your card can inject
-  * The card is configured on the same channel as the AP.+  * The card is configured on the same channel as the AP.  Use "​iwconfig"​ to confirm.
   * The BSSID and ESSID (-a / -e options) are correct.   * The BSSID and ESSID (-a / -e options) are correct.
   * If Prism2, make sure the firmware was updated. ​   * If Prism2, make sure the firmware was updated. ​
fake_authentication.txt · Last modified: 2010/11/21 13:18 by sleek