@atom: Thanks. I tried lowering the value of -n from 400 to 200 and it allowed my cracking session to run a little longer. I am now able to run a dictionary attack successfully with a dictionary of size ~500 Mb.
However, with a larger dictionary, it still fails.
Yes, these hashes are highly iterated, I understand. I would like to understand how the --gpu-loops parameter is related to the number of iterations used in the hashing algorithm.
For instance, MD5(Unix) has a fixed number of 1000 iterations. How would this relate to a --gpu-loops value of, let's say, 200.
Will the GPU compute 200 iterations in one go?
Also, is the parameter, --gpu-loops only related to number of iterations computed by the GPU? Because, I also use it with unsalted hashes such as MD5 and SHA-1.
Until now, I was using the -n option.
Now, I have changed it to:
--gpu-accel=80 --gpu-loop=8
let's see, how far the attack goes.
Test 1:
Dictionary size ~1Gb
Progress before temperature limit reached: 10 %
option used, -n 200
Test 2:
Same dictionary:
--gpu-accel=80 --gpu-loops=8
temperature limit reached within 5 seconds from the start of attack :O
Test 3:
Same dictionary.
--gpu-accel=80 --gpu-loops=1
The cracking session is running, lets see how far it goes.
**** Update ****
The attack is running good with --gpu-loops=1 but yes the speed has come down a lot.
From, 430k c/s to 58k c/s
I hope, slow and steady wins the race
However, with a larger dictionary, it still fails.
Yes, these hashes are highly iterated, I understand. I would like to understand how the --gpu-loops parameter is related to the number of iterations used in the hashing algorithm.
For instance, MD5(Unix) has a fixed number of 1000 iterations. How would this relate to a --gpu-loops value of, let's say, 200.
Will the GPU compute 200 iterations in one go?
Also, is the parameter, --gpu-loops only related to number of iterations computed by the GPU? Because, I also use it with unsalted hashes such as MD5 and SHA-1.
Until now, I was using the -n option.
Now, I have changed it to:
--gpu-accel=80 --gpu-loop=8
let's see, how far the attack goes.
Test 1:
Dictionary size ~1Gb
Progress before temperature limit reached: 10 %
option used, -n 200
Test 2:
Same dictionary:
--gpu-accel=80 --gpu-loops=8
temperature limit reached within 5 seconds from the start of attack :O
Test 3:
Same dictionary.
--gpu-accel=80 --gpu-loops=1
The cracking session is running, lets see how far it goes.
**** Update ****
The attack is running good with --gpu-loops=1 but yes the speed has come down a lot.
From, 430k c/s to 58k c/s
I hope, slow and steady wins the race