GPU Crack Speed Half of Expected
#2
the commands that you use are very weird/wrong:

1. the -w that you use twice in your -a 0 (dictionary attack) is wrong. why two times -w ? one time -w without the actual workload profile

2. in the second command, you use a mask attack (-a 3) without a mask. yeah, a mask attack without a mask !? o.O
That's also very strange... are you sure that is what you are trying to run. normally you at least define and run some specific mask like:
Code:
-a 3 -w 3 --increment--increment-min 6 -a 3 hash.txt ?a?a?a?a?a?a?a?a

at the end, I think you are just confused about the comparison against the benchmark speed:
Code:
hashcat.exe -m 1000 -b

^ this benchmark run uses a single NTLM hash and therefore hashcat can apply optimizations that can't be done with multiple hashes. Benchmark also uses a very huge keyspace/mask (and workload profile, -w 3). It's the maximum speed that you only can reach in real runs if you only crack single hashes with a mask atttack (-a 3) and a similar workload profile (-w 3) and a large keyspace/mask.

It's difficult to compare against things that are not identical/similar ... i.e. it's like comparing apples to oranges.

Just try to run a benchmark or a single hash with a huge mask (and -w 3) and you will see different speeds.
Reply


Messages In This Thread
GPU Crack Speed Half of Expected - by CarbonDPG - 06-30-2020, 02:42 AM
RE: GPU Crack Speed Half of Expected - by philsmd - 06-30-2020, 07:43 AM
RE: GPU Crack Speed Half of Expected - by philsmd - 07-01-2020, 08:46 AM