08-21-2015, 02:05 PM
It is also important that you let us know about the exact version(s) of cpu hashcat. And try with the newest version (download, extract and run it).
The reason for this is: cpu hashcat previous to 0.50 did increment (-i or --increment) by default. So you might just didn't see that it started with length 1, then 2, then 3 ... (very quickly) and finally did take some more time on 6 char long passwords.
Newest cpu hashcat version have --increment, --increment-min and --increment-max similar to oclHashcat (and they do not increment the mask by default, but start at *exactly* the length of the mask if no -i or --increment was specified).
@mastercracker: --pw-min parameter does not exist anymore, it was replaced (as mentioned above, in the changes.txt file and release notes with --increment-min)
The reason for this is: cpu hashcat previous to 0.50 did increment (-i or --increment) by default. So you might just didn't see that it started with length 1, then 2, then 3 ... (very quickly) and finally did take some more time on 6 char long passwords.
Newest cpu hashcat version have --increment, --increment-min and --increment-max similar to oclHashcat (and they do not increment the mask by default, but start at *exactly* the length of the mask if no -i or --increment was specified).
@mastercracker: --pw-min parameter does not exist anymore, it was replaced (as mentioned above, in the changes.txt file and release notes with --increment-min)