07-31-2020, 10:47 PM
(07-31-2020, 09:50 PM)philsmd Wrote: either use:
Code:hashcat -m 11600 -a 3 -w 3 --increment --increment-min 8 hash.txt myword?d?d?d?d?d?d
or
Code:hashcat -m 11600 -a 6 -w 3 --increment --increment-min 2 hash.txt dict.txt ?d?d?d?d?d?d
where dict.txt contains the word(s), one per line.
Use the one method that is faster, either -a 3 or -a 6. There might be other ways to attack it (e.g. to use --slow-candidates or pipes or pre-computed dicts), but I think -a 3 and -a 6 are the most likely one that work fastest for this specific situation (a slow hash with a fixed prefix).
Perfect, the first one with a higher minimum increment and beginning of pattern is exactly what I need. Thank you.
It started to work after adding the -O argument to the command. This is probably why it was crashing before, in the information file it talks about the -O being an optimized driver for these specific platforms.
I'll let it run for the time it will take.
If it will take more than 24 hours, I know that "the very first digit after the letter strings" is "Not 0,1,2 or 3". So from 4 to 9.
Can we add this into the command to further optimize it? As my video card is pretty mediocre. Again, thank you very much, this was very helpful.