Piping speed from statsprocessor to oclhashcat
#3
(09-05-2013, 05:46 PM)atom Wrote: Depending on the algorithm you use, this speed sounds to low. For example if this is MD5, you should be in den 500M or more range. If thats so, you might have forgotten to add rules as a multiplier. This is required to get maximum speed.

Hi atom!

All the hashes I'm trying to crack are on MD5...

This is what I'm getting after I add a rule (best64)

Starting attack in stdin mode...


Session.Name...: cudaHashcat-plus
Status.........: Aborted
Rules.Type.....: File (rules\best64.rule)
Input.Mode.....: Pipe
Hash.Target....: File (C:\Users\eXPeri3nc3\Desktop\md5.txt)
Hash.Type......: MD5
Time.Started...: Fri Sep 06 00:18:12 2013 (5 mins, 44 secs)
Speed.GPU.#1...: 169.8 MH/s
Recovered......: 0/5556 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 53715517440
Rejected.......: 0
HWMon.GPU.#1...: 6% Util, 63c Temp, N/A Fan

Started: Fri Sep 06 00:18:12 2013
Stopped: Fri Sep 06 00:23:56 2013

Much faster! However, like what you've said, I normally run a dictionary cracking at the speed of 450.0 MH/s so this is still 1/3 of it.

Can you please explain why the rule is needed as a multiplier?

--

Also, one question on statprocessor. If you run the same output twice, will the output be statistically the same?

Thanks a lot!


Messages In This Thread
RE: Piping speed from statsprocessor to oclhashcat - by eXPeri3nc3 - 09-05-2013, 06:27 PM