shared_key
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
shared_key [2007/06/25 18:38] – darkaudax | shared_key [2010/11/20 23:53] – typo sleek | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Tutorial: How to do shared key fake authentication ? ====== | ====== Tutorial: How to do shared key fake authentication ? ====== | ||
- | Version: 1.06 June 25, 2007\\ | + | Version: 1.08 November 7, 2008\\ |
By: darkAudax | By: darkAudax | ||
File linked to this tutorial: [[http:// | File linked to this tutorial: [[http:// | ||
- | |||
===== Introduction ===== | ===== Introduction ===== | ||
Line 18: | Line 17: | ||
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:// | + | 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 31: | Line 30: | ||
Ensure all of the above assumptions are true, otherwise the advice that follows will not work. In the examples below, you will need to change " | Ensure all of the above assumptions are true, otherwise the advice that follows will not work. In the examples below, you will need to change " | ||
- | |||
- | In the examples, the option " | ||
===== Equipment used ===== | ===== Equipment used ===== | ||
Line 61: | Line 58: | ||
==== Solution Overview ==== | ==== Solution Overview ==== | ||
- | In order to do a shared key fake authentication, | + | In order to do a shared key fake authentication, |
Here are the basic steps we will be going through: | Here are the basic steps we will be going through: | ||
Line 110: | Line 107: | ||
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 MAC address of the card in the AP field, other drivers do no. 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 MAC address of the card in the AP field, other drivers do no. 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/# | + | |
=== Troubleshooting Tips === | === Troubleshooting Tips === | ||
Line 122: | Line 118: | ||
Open another console session to capture the PRGA xor file. Then enter: | Open another console session to capture the PRGA xor file. Then enter: | ||
- | airodump-ng -c 9 - -bssid 00: | + | airodump-ng -c 9 --bssid 00: |
Where: | Where: | ||
*-c 9 is the channel for the wireless network | *-c 9 is the channel for the wireless network | ||
- | *- -bssid 00: | + | *-'''' |
*-w sharedkey is file name prefix for the file which will contain the PRGA xor data. | *-w sharedkey is file name prefix for the file which will contain the PRGA xor data. | ||
*ath0 is the interface name. | *ath0 is the interface name. | ||
- | Beyond the error message shown in the introduction, | + | Beyond the error message shown in the introduction, |
CH 9 ][ Elapsed: 20 s ][ 2007-02-10 16:29 | CH 9 ][ Elapsed: 20 s ][ 2007-02-10 16:29 | ||
Line 136: | Line 132: | ||
BSSID PWR RXQ Beacons | BSSID PWR RXQ Beacons | ||
- | 00: | + | 00: |
BSSID STATION | BSSID STATION | ||
Line 142: | Line 138: | ||
00: | 00: | ||
- | Once "PSK" appears on the airodump-ng screen, do file listing and it will look something like: | + | Once "SKA" appears on the airodump-ng screen |
| | ||
Line 164: | Line 160: | ||
Where: | Where: | ||
* -0 means deauthentication | * -0 means deauthentication | ||
- | * 1 is the number of deauths to send (you can send muliple | + | * 1 is the number of deauths to send (you can send multiple |
* -a 00: | * -a 00: | ||
* -c 00: | * -c 00: | ||
Line 173: | Line 169: | ||
| | ||
- | Prior to executing the command above, open another console and start airodump-ng in the same way as you did earlier " | + | Prior to executing the command above, open another console and start airodump-ng in the same way as you did earlier " |
Once you run the deauthentication command, see if airodump-ng has output the PRGA xor file. If not, try another deauthentication or against another client. | Once you run the deauthentication command, see if airodump-ng has output the PRGA xor file. If not, try another deauthentication or against another client. |
shared_key.txt · Last modified: 2018/03/11 20:19 by mister_x