Sure, but still 31 chars would be good. In fact, 63 chars would be good. (why not, if it doesn't slow down the bruteforcing?) Because otherwise one has still to use other tools :\
Suggestion: You have several tools, maybe you can merge some of them?
I must say only the full range of chars is enough..because even if other tools do not scale so good, at least for me waiting 4h instead of 2 and knowing of having tested to whole list is better than not having tested the other 10-15% of my wordlist's words. (and again, why not removing the limit if it doesn't slow down the bruteforcing?)
-------------
Suggestion: You have several tools, maybe you can merge some of them?
I must say only the full range of chars is enough..because even if other tools do not scale so good, at least for me waiting 4h instead of 2 and knowing of having tested to whole list is better than not having tested the other 10-15% of my wordlist's words. (and again, why not removing the limit if it doesn't slow down the bruteforcing?)
-------------
Quote:Input.Mode: Dict (../opencrack_plains.txt):\ What does "Index.....: 2/2" mean?
Index.....: 1/2 (segment), 3145161 (words), 33550340 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: 741 plains, 741 words
Progress..: 3145161/3145161 (100.00%)
Running...: 00:01:10:44
Estimated.: --:--:--:--
Input.Mode: Dict (../opencrack_plains.txt)
Index.....: 2/2 (segment), 3426892 (words), 33381465 (bytes)
Recovered.: 0/1 hashes, 0/1 salts
Speed/sec.: 711 plains, 711 words
Progress..: 65732/3426892 (1.92%)
Running...: 00:00:01:32
Estimated.: 00:01:18:47
^CTo restore Session use Parameter -s 3225529