03-27-2012, 04:20 PM
I think this whole thread is an extension of the “Pseudo Markov†request I made earlier.
I personally believe that the functionality to allow the user the ability to make rules on how hascatplus should generate a brute force list will make one of the most significant reductions in crack time since hashcatplus started using GPU’s instead of CPU’s.
I am guessing that ZerXes was meaning the cracking process as a whole rather than actually speeding up keys tested per second. As the keyspace would be so dramatically reduced by giving the user the ability to narrow down the possible combinations it may yield the “equivalent†cracking speed as ZerXes implies. I’m only guessing that’s what he meant.
I personally believe that the functionality to allow the user the ability to make rules on how hascatplus should generate a brute force list will make one of the most significant reductions in crack time since hashcatplus started using GPU’s instead of CPU’s.
(03-27-2012, 03:18 PM)atom Wrote: How does limiting the keyspace increase the overall speed?
I am guessing that ZerXes was meaning the cracking process as a whole rather than actually speeding up keys tested per second. As the keyspace would be so dramatically reduced by giving the user the ability to narrow down the possible combinations it may yield the “equivalent†cracking speed as ZerXes implies. I’m only guessing that’s what he meant.