Please note, this is a STATIC archive of website hashcat.net from October 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.
hashcat Forum
time estimate for brute forcing wpa2 - 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: time estimate for brute forcing wpa2 (/thread-1832.html)



time estimate for brute forcing wpa2 - rewre - 12-12-2012

Hello

Need to know some time estimate on brute forcing a wpa2 key with a length of 13 and only consisting of capitals (A-Z) and digits (0-9).

Planning to buy a HD5850 only for this job.

Is this worth the trouble or is it gonna more than a week?


(already a sorry if there's a calculator available somewhere or/and i didnt do enough searching)


RE: time estimate for brute forcing wpa2 - radix - 12-12-2012

longer than a week


RE: time estimate for brute forcing wpa2 - gat3way - 12-12-2012

I am afraid humans will be already extinct long before it processes the whole keyspace.


RE: time estimate for brute forcing wpa2 - M@LIK - 12-12-2012

91403960 years only.


RE: time estimate for brute forcing wpa2 - rewre - 12-12-2012

Ok got it! Wink

Got a bit wiser in these few minutes.

Thanks and keep up the good work!


RE: time estimate for brute forcing wpa2 - forumhero - 12-12-2012

what i do to get a rough estimate.

look up gpu speeds, i like to use https://golubev.com/gpuest.html
the formula (charset^keylength)/gpuspeed
use google to convert seconds to hours/days/months/years/etc., so from google search type:

((36^13)/60672) seconds to years

results: 89,094,215 years