03-10-2016, 08:29 PM
(03-10-2016, 08:06 PM)philsmd Wrote: I see many problems here.
1. maskprocessor does not support .hcmask files, you can see this easily yourself by checking the output of the maskprocessor command (mp64.exe)
2. there are limitations on the max. password length in place to allow several optimizations: see https://hashcat.net/wiki/frequently_aske...ord_length
3. the .hcstat file is only used by statsprocessor or oclHashcat/cudaHashcat by using certain attack modes only. oclHashcat will check if the file is valid, but in your case, by using -a 0, it isn't really involved at all, only when you use -a 3 (mask attack) it will be involved
4. your keyspace is incredible large, it is: (26 + 10) ^ 64 - (negligible few candidates) ~ 4,011,991,914,547,630,480,065,053,387,702,443,812,690,402,487,741,812,225,955,731,622,655,455,723,258,857,248,542,161,222,254,985,216 (try reading this aloud)
You should easily have found these (and many more) facts by just reading the documentation (wiki/faq/forum) or just by searching for this info e.g. "maximum supported password length"
Oops! I'm sorry for not checking, but I read somewhere that you can recompile it to change the max password length, and when I checked it said it was 64. But I just remembered that was only for statsprocessor. My rationale was that it would possibly work because of the -r and -q parameters because I asked a statistics professor how many possible combinations with length 64 and with max 8 of the same characters and max 2 consecutive characters (by accident) and I believe he said it would be somewhere around ~10^19 so I thought that max 3 consecutive characters would reduce that number heavily. Do you see my problem even being solvable with oclHashcat? At this point, I've exhausted all of my ideas
