Post: How To Check If You Have a Valid WPA Handshake in Kali
Options
10-30-2015, 06:18 PM
#1
Hydrogen
Super Mod
*Kali
*.CAP file
Okay, so when capturing a handshake, you can sometimes capture a incomplete handshake. It will come up as if you captured one, but you will be unable to brute force it. So instead of wasting hours of your time brute forcing the handshake, I will show you two methods on how to check if its valid before you go ahead and brute force.
Method 1: Cowpatty
1.) Open up CMD and type in the following command:
CODE:
cowpatty -c -r FONHandShake.cap
REPLACE FONHandShake.cap WITH THE NAME OF YOUR .CAP FILE WHICH SHOULD BE IN THE HOME DIRECTORY.
Once you run that command you should get the results of the quality of the handshake.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Method 2: Pyrit
1.) In CMD type the following command
CODE:
pyrit -r FONHandShake.cap analyze
REPLACE FONHandShake.cap WITH THE NAME OF YOUR .CAP FILE WHICH SHOULD BE IN THE HOME DIRECTORY.
You will get the results which will state if the handshake is good or not(good/workable/bad).
If you have a good quality handshake it should have the word "Good" in there.
Cheers, Lwja
The following user thanked Hydrogen for this useful post:
11-11-2015, 06:41 AM
#2
Rath
Today Will Be Different
Originally posted by Lwja
***Requirements***:
*Kali
*.CAP file
Okay, so when capturing a handshake, you can sometimes capture a incomplete handshake. It will come up as if you captured one, but you will be unable to brute force it. So instead of wasting hours of your time brute forcing the handshake, I will show you two methods on how to check if its valid before you go ahead and brute force.
Method 1: Cowpatty
1.) Open up CMD and type in the following command:
CODE:
cowpatty -c -r FONHandShake.cap
REPLACE FONHandShake.cap WITH THE NAME OF YOUR .CAP FILE WHICH SHOULD BE IN THE HOME DIRECTORY.
Once you run that command you should get the results of the quality of the handshake.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Method 2: Pyrit
1.) In CMD type the following command
CODE:
pyrit -r FONHandShake.cap analyze
REPLACE FONHandShake.cap WITH THE NAME OF YOUR .CAP FILE WHICH SHOULD BE IN THE HOME DIRECTORY.
You will get the results which will state if the handshake is good or not(good/workable/bad).
If you have a good quality handshake it should have the word "Good" in there.
Cheers, Lwja
*Kali
*.CAP file
Okay, so when capturing a handshake, you can sometimes capture a incomplete handshake. It will come up as if you captured one, but you will be unable to brute force it. So instead of wasting hours of your time brute forcing the handshake, I will show you two methods on how to check if its valid before you go ahead and brute force.
Method 1: Cowpatty
1.) Open up CMD and type in the following command:
CODE:
cowpatty -c -r FONHandShake.cap
REPLACE FONHandShake.cap WITH THE NAME OF YOUR .CAP FILE WHICH SHOULD BE IN THE HOME DIRECTORY.
Once you run that command you should get the results of the quality of the handshake.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
Method 2: Pyrit
1.) In CMD type the following command
CODE:
pyrit -r FONHandShake.cap analyze
REPLACE FONHandShake.cap WITH THE NAME OF YOUR .CAP FILE WHICH SHOULD BE IN THE HOME DIRECTORY.
You will get the results which will state if the handshake is good or not(good/workable/bad).
If you have a good quality handshake it should have the word "Good" in there.
Cheers, Lwja
Moved to Internet Talk as this is more along the lines of what you'd find in this section.
Copyright © 2024, NextGenUpdate.
All Rights Reserved.
