06-21-2012, 10:17 AM
Its the opposite. The higher the -t value, the bigger the keyspace, the more you crack. Only exception is the value 0, which completly disables the threshold (actually, it sets it to 256).
Also, this algorithm is not a dictionary. Chances are high that it generates "123" but there is no guarantee (well, at least as long as you do not use -t 0).
The rejection thing is clear. Once a salt (not a hash) has been cracked, it will be sorted out. There is no need to add it to the hashing iteration pool since it will not crack any hash. Thats why they are skipped. In this case, its added to the rejection counter. Thats required to keep up showing the correct ETA plus not adding these to the speed counter.
Also, this algorithm is not a dictionary. Chances are high that it generates "123" but there is no guarantee (well, at least as long as you do not use -t 0).
The rejection thing is clear. Once a salt (not a hash) has been cracked, it will be sorted out. There is no need to add it to the hashing iteration pool since it will not crack any hash. Thats why they are skipped. In this case, its added to the rejection counter. Thats required to keep up showing the correct ETA plus not adding these to the speed counter.