Ticket #718 (new defect)
Aircrack-ng 1.0 final does not recover the WEP key for the dictionary attack (hexadecimal)
| Reported by: | enterprise | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | N/A |
| Component: | aircrack-ng | Version: | 1.0 |
| Keywords: | Cc: |
Description
Attn. Aircrack-NG's BTS.
I should clarify that I do not speak English, so I use a translator. I realize that may not be able to express myself, so I'll still be able to interpret correctly what I will try to explain:
I would like to report that detected a possible bug in Aircrack-ng 1.0 final when trying to retrieve the WEP key when I use the dictionary attack (hex).
With a single capture, the attack Aircrack PTW 1.0 final retrieves the password correctly, but using the dictionary attack WEP (hex) fails. The dictionary attack is created for the hexadecimal, 26 digits plus ":" and contains the password you want to retrieve.
The syntax used for dictionary attack was as follows:
aircrack-ng-w h: dicc.txt-a 1 file.cap
for the PTW attack was used as follows:
aircrack-ng-a 1 file.cap
As further evidence I have used airdecap-ng getting for what application decrypts all packets (110,891) of which 220 were plain text.
As a consequence the resulting files (dec.cap & bad.cap) can not be used by aircrack-ng they either have been decrypted (dec.cap) or lacking (bad.cap).
This leads me to think that if airdecap-ng decrypts these packets how is it possible that Aircrack-ng (using the dictionary attack) can not do?.
As an interesting note that in the failed attack Aircrack Dictionary shows that it has test 0 keys, as I said when the dictionary contains the key.
So far I tried aircrack-ng-1.0-tar.gz for Linux with Aircrack-ng VMware
For the Windows version (aircrack-ng-1.0-win.zip) I tested on XP, Vista and Win 7
both yielded the same result: PTW retrieves the key while the dictionary attack aircrack 1.0 final does not.
These were my results and I communicate well. Sorry can not make the correction to the problem as far I know that it can be.
The file.cap and the dicc.lst and screenshots are available for the / s persons approved by the site administrator to test whether these tests are required (as long as these are not published because they contain private data ).
The sending of these can be done by a pathway that ensures your privacy and Vds recommended.
Att. Enterprise.
