cudaHashcat-plus64 on Debian fails when using a known password - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html) +--- Forum: Very old oclHashcat-plus Support (https://hashcat.net/forum/forum-23.html) +--- Thread: cudaHashcat-plus64 on Debian fails when using a known password (/thread-1584.html) |
cudaHashcat-plus64 on Debian fails when using a known password - clamore2 - 09-21-2012 I wanted to try how well cudaHashcat plus did against aircrack, so I captured the WPA2-CCMP handshake of my own network and tried to crack it both with aircrack and cudaHashcat using the example.dict that comes with hashcat and adding my network password inside it. Long story short, aircrack cracked it, but hashcat failed: it "Exhausted" the dictionary without recognizing the password. My steps were: airodump-ed a 4-way handshake between my phone and the router, wpaclean-ed it, used "aircrack <capfile> -J <hccapfile>" to generate the hccap file and launched $ aircrack-ng -w /tmp/dic /tmp/hashcat.hccap and $ ./cudaHashcat-plus64.bin -m 2500 /tmp/hashcat.hccap /tmp/dic2 while the first succeded, the second resulted in: Code: cudaHashcat-plus v0.09 by atom starting... Any ideas about why this happened? Thanks! RE: cudaHashcat-plus64 on Debian fails when using a known password - M@LIK - 09-21-2012 Your password must be 8 min 15 max in length. RE: cudaHashcat-plus64 on Debian fails when using a known password - yiurunk - 11-30-2012 I'm having the same exact issue as OP. How is the key length the issue since it has an allowable key length up to 64 characters? It's obviously working with different applications to find keys larger than 15 chars. So is it something else or am I missing something? Thanks for your help! RE: cudaHashcat-plus64 on Debian fails when using a known password - undeath - 11-30-2012 oclhashcat-plus does this for performance reasons. It is implemented that way and you can't change anything about it. RE: cudaHashcat-plus64 on Debian fails when using a known password - yiurunk - 11-30-2012 (11-30-2012, 12:38 AM)undeath Wrote: oclhashcat-plus does this for performance reasons. It is implemented that way and you can't change anything about it. Ah well that explains it! ... and that sucks. So if I were to recompile with a longer space what are the drawbacks besides a perceived incredibly long calculation time? Thanks for the quick reply undeath. RE: cudaHashcat-plus64 on Debian fails when using a known password - atom - 12-08-2012 Well not for WPA/WPA2 but for other algorithms. There has been a lot of talks on the max. length 15 restriction but still none of them convinced me to overcome with this limit and rewrite the base classes. Also it would require a lot more memory. My main argument is still that the chances to crack 15+ passwords is VERY unusual for whatever algorithm. Only if the passwords is really really bad and in this case you have it in your dictionary and can crack it with aircrack-ng. RE: cudaHashcat-plus64 on Debian fails when using a known password - qweasd - 12-09-2012 I would like to point out that there is a CUDA version of aircrack-ng: https://trac.aircrack-ng.org/svn/branch/aircrack-ng-cuda/ i really doubt it's as fast as hashcat though. |