Stats Processor Spitting Out Junk
#2
statsprocessor is built into oclHashcat and used by default anywhere a mask is used, so the only reason to use statsprocessor is to add oclHashcat-style per-position markov support to other applications that do not have it (cpu hashcat, john the ripper, etc.) i mention this to make sure you are not piping statsprocessor into oclHashcat since you mentioned your GPU and the APP SDK.

oclHashcat's markov implementation is per-position and based around mask attacks. Therefore the threshold needs to be less than the number of combinations for each position. For example ?l only has 26 possible combinations so -t needs to be < 26 to have any effect.

Without -t, or with a -t value greater than the possible number of combinations in each mask position, oclHashcat will simply do a probabilistically-ordered brute force. So you'll still be brute forcing the same keyspace, just in a different order.

In either case they aren't random, even if they appear to be nonsensical. They are probabilistically ordered based on the character position, adjacent character, and length. The reason you may not be seeing very many real words is because you are currently using a length of 5, and there probably aren't that many 5-character passwords in your training set.


Messages In This Thread
RE: Stats Processor Spitting Out Junk - by epixoip - 07-28-2014, 04:02 AM