search

orlov-vo / pyrit

Automatically exported from code.google.com/p/pyrit
0 stars 0 forks source link

failure to detect any handshakes (including in test dump files from source) #424

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run 'analyze' against any dump file within the test/ directory
OR  
1. Run attack_passthrough against a dump file known to contain a valid WPA 
handshake

e.g.:
$ pyrit -r /opt/pyrit-read-only/pyrit/test/wpapsk-linksys.dump.gz analyze
Pyrit 0.4.1-dev (svn r308) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+
Parsing file '/opt/pyrit-read-only/pyrit/test/wpapsk-linksys.dump.gz' (1/1)...
Parsed 6 packets (6 802.11-packets), got 1 AP(s)
#1: AccessPoint 00:0b:86:c2:a4:85 ('linksys'):
  #1: Station 00:13:ce:55:98:ef
No valid EAOPL-handshake + ESSID detected.

What is the expected output? What do you see instead?
Identification of a valid WPA handshake for cracking.

What version of the product are you using? On what operating system?
Clean install, without errors, via SVN source: Pyrit 0.4.1-dev (svn r308)
Red Hat 4.6.2-2 Amazon Linux AMI release 2012.09 (Linux version 
3.2.37-2.47.amzn1.x86_64)

Please provide any additional information below.
No handshakes are detected for any of the dump files included in the test 
directory:
wpa2psk-2WIRE972.dump.gz
wpa2psk-MOM1.dump.gz
wpapsk-linksys.dump.gz
test_pyrit.py
wpa2psk-linksys.dump.gz
wpa2psk-Red_Apple.dump.gz
wpapsk-virgin_broadband.dump.gz

Likewise for locally-created capture files (that aircrack and cowpatty confirm 
contain valid handshakes). 

No other errors have been encountered during the installation or testing or 
pyrit, including list_cores, selftest, benchmark:
[ec2-user@ip-10-16-3-184 ~]$ pyrit selftest
Pyrit 0.4.1-dev (svn r308) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+
Cores incorporated in the test:
#1:  'CUDA-Device #1 'Tesla M2050''
#2:  'CUDA-Device #2 'Tesla M2050''
#3:  'CPU-Core (SSE2)'
<snip>
Running selftest...
All results verified. Your installation seems OK

Original issue reported on code.google.com by ber...@gmail.com on 1 Apr 2013 at 7:08

GoogleCodeExporter commented 9 years ago 
This is the same kind of thing I keep getting too, I used both Aircrack and 
Kismet, Aircrack confirms a valid captured WPA handshake, but Pyrit doesn't 
recognize it. Kismet can also capture data packets too, even captures valid WPA 
handshakes but Pyrit fails to read them.

Original comment by shadwol...@gmail.com on 17 May 2013 at 6:43