Hashcat stop randomly

[aquaweer]

Hi...

My session stops randomly everytime @ one point 

Does someone knows the solutions for this ?



pull/1273/head Version

Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: 7f1e7xxxxxxxxxxxxx
Time.Started.....: Fri Aug 11 17:58:17 2017 (3 secs)
Time.Estimated...: Fri Aug 11 17:59:49 2017 (1 min, 29 secs)
Guess.Base.......: File (/root/Lst2/Top2Billion_probable.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....: 20127.2 kH/s (1.50ms)
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 62914574/1866618273 (3.37%)
Rejected.........: 14/62914574 (0.00%)
Restore.Point....: 62914574/1866618273 (3.37%)
Candidates.#2....: trapsl -> skuvat1
HWMon.Dev.#2.....: Temp: 52c Fan:  0% Util: 44% Core:1961MHz Mem:3802MHz Bus:8

Cracking performance lower than expected? Append -w 3 to the commandline.

Approaching final keyspace - workload adjusted.           

Session..........: hashcat                                
Status...........: Exhausted
Hash.Type........: MD5
Hash.Target......: 7fxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Time.Started.....: Fri Aug 11 17:58:17 2017 (1 min, 35 secs)
Time.Estimated...: Fri Aug 11 17:59:52 2017 (0 secs)
Guess.Base.......: File (/root/Lst2/Top2Billion_probable.txt)
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....: 20453.4 kH/s (1.49ms)
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 1866618273/1866618273 (100.00%)
Rejected.........: 3050530/1866618273 (0.16%)
Restore.Point....: 1866618273/1866618273 (100.00%)
Candidates.#2....: 0121j -> ````````````````````````````
HWMon.Dev.#2.....: Temp: 58c Fan:  0% Util: 43% Core:1949MHz Mem:3802MHz Bus:8

Started: Fri Aug 11 17:58:15 2017
Stopped: Fri Aug 11 17:59:53 2017

[philsmd]

Why do you think it stopped without reasons?

From the output you have posted above it seems that everything is working correctly.
I don't see any evidence that there is something strange going on.

It calculated an approximated run time of 1 1/2 minutes at the very start and a keyspace of 1866618273 password candidates and after the 1 and 1/2 minutes it finished everything with 100% (1866618273 of 1866618273).

There is no evidence of a "random stop" from the output above.

It just exhausted the full keyspace (without a crack), see this line:

Status...........: Exhausted

This means that the whole keyspace was exhausted (all password candidates have been tested).

Please be more specific about your problem, because I do not see any problem at all.

[aquaweer]

Idd nevermind ..

But now i dont find any password

what is the best bruteforce command to crack this ? or does someone knows more good wordlist?

thnx

[aquaweer]

somebody can help me please??