Exhausted?

[Toil]

When I'm running this command:

./hashcat-ocl-64.bin -c 500 --gpu-accel 160 --gpu-loops 1024 -n 800 --remove -m 0 uncracked.txt -o cracked.txt -a 3 -1 ?l?d?s?u?h ?1


I get;


Status.......: Exhausted
Input.Mode...: Mask (?1)
Hash.Target..: File (uncracked.txt)
Hash.Type....: MD5
Time.Running.: 1 sec
Time.Left....: 0 secs
Time.Util....: 1025.5ms/168.4ms Real/CPU, 19.7% idle
Speed........: 153 c/s Real, 26611 c/s GPU
Recovered....: 0/2456 Digests, 0/1 Salts
Progress.....: 157/157 (100.00%)
Rejected.....: 0/157 (0.00%)
HWMon.GPU.#1.: 35% Util, 45c Temp, 10% Fan

I'm using a 7970, and it works with wordlists, etc, and other masks, with other hash lists.

Any idea why it's happening?


Thanks

[dikiy]

Input.Mode...: Mask (?1)
Progress.....: 157/157 (100.00%)

You set 1 byte long mask (?1) and hashcat exhausted all 157 available password variations. You should supply longer mask (?1?1 and so on), also check for -i flag

http://hashcat.net/wiki/doku.php?id=mask_attack

[Toil]

Input.Mode...: Mask (?1)
Progress.....: 157/157 (100.00%)

You set 1 byte long mask (?1) and hashcat exhausted all 157 available password variations. You should supply longer mask (?1?1 and so on), also check for -i flag

http://hashcat.net/wiki/doku.php?id=mask_attack

I know about the --increment flag.
It doesn't work as expected. You can't custom set your ?1, ?2, ?3, ?4. It is always ?l?d?u.

But, what does it mean "exhausted"
Finished?

Thanks

[The Mechanic]

Exhausted means all password combinations you provided have been tried, expand your mask. -1?l?u?d = ?1?1?1?1?1?1?1?1?1?1 = 10 length max lower, upper, digit

-1?l?u -2?l?d -3?d?s ?1?2?2?3?3?3 is 6 length max, would be lower upper char for first position, 2nd and 3rd is lower and digit 4,5,6 positions would be digits and symbols.

Use the increment flag to run all combinations of the mask up to the length you provide or specify no mask and use the build in set

[epixoip]

I know about the --increment flag. It doesn't work as expected. You can't custom set your ?1, ?2, ?3, ?4. It is always ?l?d?u.

false.

But, what does it mean "exhausted"
Finished?

yes, it means you have exhausted the given keyspace without finding the password.

[Toil]

I know about the --increment flag. It doesn't work as expected. You can't custom set your ?1, ?2, ?3, ?4. It is always ?l?d?u.

false.

But, what does it mean "exhausted"
Finished?

yes, it means you have exhausted the given keyspace without finding the password.

$ cat o
0610a910e9cd7ec9f78b7e3f4d959e6f


$ ./hashcat-ocl-64.bin -c 500 --gpu-accel 160 --gpu-loops 1024 -n 800 o -a 3 -1 ?l?d?s?u --increment --force

Code:

$ ./hashcat-ocl-64.bin -c 500 --gpu-accel 160 --gpu-loops 1024 -n 800 o -a 3 -1 ?l?d?s?u -2 ?l?d?s?u --increment  --force
oclHashcat-plus v0.09 by atom starting...

Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Workload: 1024 loops, 800 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Tahiti, 2957MB, 925Mhz, 32MCU
Device #1: Kernel ./kernels/4098/m0000_a3.Tahiti_938.2_1.4.1741.kernel (387048 bytes)

[s]tatus [p]ause [r]esume [b]ypass [q]uit => s
Status.......: Running
Input.Mode...: Mask (?1?2?2?2)
Hash.Target..: 0610a910e9cd7ec9f78b7e3f4d959e6f
Hash.Type....: MD5
Time.Running.: 0 secs
Time.Left....: 0 secs
Time.Util....: 137.7ms/0.0ms Real/CPU, 0.0% idle
Speed........:        0 c/s Real,        0 c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 0/80352 (0.00%)
Rejected.....: 0/0 (0.00%)
HWMon.GPU.#1.: 31% Util, 40c Temp, 10% Fan
[s]tatus [p]ause [r]esume [b]ypass [q]uit => s
Status.......: Running
Input.Mode...: Mask (?1?2?2?2?2?2)
Hash.Target..: 0610a910e9cd7ec9f78b7e3f4d959e6f
Hash.Type....: MD5
Time.Running.: 0 secs
Time.Left....: 0 secs
Time.Util....: 218.5ms/169.0ms Real/CPU, 341.7% idle
Speed........:        0 c/s Real,        0 c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 0/3748902912 (0.00%)
Rejected.....: 0/0 (0.00%)
HWMon.GPU.#1.: 31% Util, 40c Temp, 10% Fan
[s]tatus [p]ause [r]esume [b]ypass [q]uit => q
                                            
Status.......: Aborted
Input.Mode...: Mask (?1?2?2?2?2?2)
Hash.Target..: 0610a910e9cd7ec9f78b7e3f4d959e6f
Hash.Type....: MD5
Time.Running.: 1 sec
Time.Left....: 0 secs
Time.Util....: 1149.2ms/169.0ms Real/CPU, 17.2% idle
Speed........:  2919.9M c/s Real,  6088.5M c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 3355443200/3748902912 (89.50%)
Rejected.....: 0/3355443200 (0.00%)
HWMon.GPU.#1.: 31% Util, 41c Temp, 10% Fan

Started: Mon Dec 24 22:46:10 2012
Stopped: Mon Dec 24 22:46:12 2012

$ ./hashcat-ocl-64.bin -c 500 --gpu-accel 160 --gpu-loops 1024 -n 800 o -a 3 -1 ?l?d?s?u -2 ?l?d?s?u ?1?1?1?1 --force

Code:

oclHashcat-plus v0.09 by atom starting...

Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Workload: 1024 loops, 800 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Tahiti, 2957MB, 925Mhz, 32MCU
Device #1: Kernel ./kernels/4098/m0000_a3.Tahiti_938.2_1.4.1741.kernel (387048 bytes)

0610a910e9cd7ec9f78b7e3f4d959e6f:123!        
                                            
Status.......: Cracked
Input.Mode...: Mask (?1?1?1?1)
Hash.Target..: 0610a910e9cd7ec9f78b7e3f4d959e6f
Hash.Type....: MD5
Time.Running.: 1 sec
Time.Util....: 1028.2ms/168.4ms Real/CPU, 19.6% idle
Speed........: 79214.1k c/s Real,  4241.3M c/s GPU
Recovered....: 1/1 Digests, 1/1 Salts
Progress.....: 81450625/81450625 (100.00%)
Rejected.....: 0/81450625 (0.00%)
HWMon.GPU.#1.: 28% Util, 41c Temp, 10% Fan

Started: Mon Dec 24 22:46:49 2012
Stopped: Mon Dec 24 22:46:51 2012

wot wot

am i doing it wrong

[M@LIK]

am i doing it wrong

Yes, you're doing it wrong.

1st, your commands are ugly, stack them properly.
2nd, your use of the -c parameter with a brute-force attack is extremely ignorant.
3rd, since you haven't provided any mask in the first attack, -plus uses the default masks and that's why your hash wasn't cracked.
4th, in the second attack you added a mask "?1?1?1?1" which fits your password, that's why it's cracked.