Distributed Workload - Keyspace

Open nicbrink opened this issue 8 years ago • 1 comments

I think there may be a bug in hashcat, which get reflected in hashview when using the hashcat start and limit features. I am hoping someone can take a look and confirm if this is the case.

If you run '--keyspace' with the mask ?a?a?a?a?a?a?a?a you get back 7,737,809,375. However when you run hashcat without the -s -l you get a restore point of 735,091,890,625.

I have done a number of trials against a random 8char hash. If I set the chunk size to 1,000,000,000 the task is broken into 8 jobs that take about 30 min to run and never cracks the hash. If I dont breakup the job if runs for considerable longer before cracking the hash.

Sep 11 '17 00:09 nicbrink

As i understand it, --keyspace isn't the EXACT number of possible characters. (Though you think it would be).

Nov 19 '18 23:11 i128