WPA2 - not working vs aircrack-ng? - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-45.html) +--- Thread: WPA2 - not working vs aircrack-ng? (/thread-5825.html) Pages:
1
2
|
WPA2 - not working vs aircrack-ng? - bastibasti - 09-01-2016 Hi, I have captured my own 4-way handshake. I know my password so I've put it at the end of my wordlist. (for testing) aircrack-ng is able to find the password easily (but sloooooooooowwww) - now I have extracted the hcap via aircrack-ng -J option hashcat cannot find the password. the only thing... the current testfile contains 100 words with a special character (aircrack skips it) and then my passphrase. could that be confusing hashcat? Code: hashcat-3.10 # ./hashcat32.bin -m 2500 3.hccap.hccap common_passwords_from_hacked_websites2.txt RE: WPA2 - not working vs aircrack-ng? - jodler303 - 09-01-2016 Just guessing. 1) Rejected.......: 30/100 (30.00%) ... are you sure your password hasn't been rejected. I'd try with a second passwordfile that ONLY has your password and see if it gets rejected or not. 2) Do you have multiple handshakes stored in that .cap file when converting it to .hccap with aircrack-ng -J ? If yes, try isolating one handshake to another .cap and then convert that to .hccap using aircrack-ng. Have a look here: https://hashcat.net/forum/thread-5792-post-31068.html#pid31068 RE: WPA2 - not working vs aircrack-ng? - bastibasti - 09-01-2016 I have done a little testing... The hccap contains exactly 1 hash, the wpa.cap contained multiple, but aircrack lets you select 1 network to export. (I selected my own) the password is rather long. 41 characters if I delete everything but my password the result is the same (the rejected rate is 0/1) Code: client1 hashcat-2.00 # ./hashcat-cli32.bin -m 2500 3.hccap.hccap common_passwords_from_hacked_websites2.txt Code: client1 cudaHashcat-2.01 # ./cudaHashcat32.bin -m 2500 3.hccap.hccap common_passwords_from_hacked_websites2.txt (09-01-2016, 04:01 PM)jodler303 Wrote: Just guessing. RE: WPA2 - not working vs aircrack-ng? - vom - 09-01-2016 Try using cap2hccap locally: https://sourceforge.net/projects/cap2hccap/ Get that - compile it - and see if you get better/expected results. PS: Why are you running older versions of (cuda)hashcat in some of your outputs ? RE: WPA2 - not working vs aircrack-ng? - atom - 09-01-2016 Sometimes it's requred to use wpaclean (part of aircrack-ng) before using cap2hccap. RE: WPA2 - not working vs aircrack-ng? - bastibasti - 09-01-2016 >Sometimes it's requred to use wpaclean (part of aircrack-ng) before using cap2hccap. the file is already clean due to its origin (wpaclean doesnt change the file) >PS: Why are you running older versions of (cuda)hashcat in some of your outputs ? for comparison I've tried those 4 versions. same hcap file, same wordlist cpuhashcat 2.0 -> OK cudahashcat 2.1 -> NG hashcat 3.0 -> NG hashcat 3.1 -> NG Now compiling wine so I can use the 32bit binary.exe Are you guys really using windows? RE: WPA2 - not working vs aircrack-ng? - atom - 09-01-2016 IOW, it never worked on GPU. Did you try hashcat 3.1 in CPU mode? RE: WPA2 - not working vs aircrack-ng? - bastibasti - 09-01-2016 (09-01-2016, 07:03 PM)atom Wrote: IOW, it never worked on GPU. Did you try hashcat 3.1 in CPU mode? Sorry to ask, but how?? I checked the docs and it seems it only accepts the gpu as available device. --opencl-platforms | Str | OpenCL platforms to use, separate with comma | --opencl-platforms=2 -D, --opencl-device-types | Str | OpenCL device-types to use, separate with comma | -D 1 [ OpenCL Device Types ] - # | Device Type ===+============= 1 | CPU 2 | GPU 3 | FPGA, DSP, Co-Processor --opencl-platforms=1 <- nvidia device --opencl-platforms=2 <- not available Code: client1 hashcat-3.10 # ./hashcat32.bin -m 2500 --opencl-platforms=2 test.hccap common_passwords_from_hacked_websites.txt and also Code: client1 hashcat-3.10 # ./hashcat32.bin -m 2500 -D 1 test.hccap common_passwords_from_hacked_websites.txt RE: WPA2 - not working vs aircrack-ng? - atom - 09-02-2016 You just need to install the OpenCL runtime for your CPU model RE: WPA2 - not working vs aircrack-ng? - bastibasti - 09-03-2016 sorry for my late reply, i had issues installing na appropriate opencl runtime on my gentoo. maybe my cpu is not supported or something. I tried to reproduce the issue on a windows machine. It behaves exactly the same. even when running the cpu opencl.... tables with 16 bits... OpenCL Platform #1: NVIDIA Corporation ====================================== - Device #1: GeForce GT 630M, skipped OpenCL Platform #2: Intel(R) Corporation ======================================== - Device #2: Intel(R) Core(TM) i7-3770S CPU @ 3.10GHz, 2037/8148 MB allocatable, 8MCU OpenCL Platform #3: Intel(R) Corporation ======================================== - Device #3: Intel(R) Core(TM) i7-3770S CPU @ 3.10GHz, 2037/8148 MB allocatable, 8MCU ..... Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts Progress.......: 2202/2202 (100.00%) Rejected.......: 0/2202 (0.00%) of course i tried that wordlist on aircrack again just for verification |