Pipe is -very- slow

[Mem5]

Hi,

I ran cudahashcat v1.37 on a small dic, and I had the message "ATTENTION!  The wordlist or mask you are using is too small....."

Ok. however it tooks ~10 seconds :

Code:

cudaHashcat-1.37>cudaHashcat64.exe -w 3 -m 0 hash.txt *.dic
..
Started: Wed Dec 02 22:05:33 2015
Stopped: Wed Dec 02 22:05:43 2015
-> 10 sec

Then I piped with hashcat 0.50  ; it tooks 2 minutes with a huge drop speed (sometimes 0 H/s, sometimes 300kH/s, instead of Mh/s without pipe)

Code:

hashcat-0.50>hashcat-cli64.exe --stdout *.dic | d:\cudaHashcat-1.37\cudaHashcat64.exe -m 0 -w 3 hash.txt

Starting attack in stdin mode...


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (10 secs)
Speed.GPU.#1...:  1048.0 MH/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 3172082
Rejected.......: 26354
HWMon.GPU.#1...:  0% Util, 45c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (20 secs)
Speed.GPU.#1...:   348.1 kH/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 6325271
Rejected.......: 33815
HWMon.GPU.#1...:  0% Util, 46c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (30 secs)
Speed.GPU.#1...:   343.4 kH/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 9474290
Rejected.......: 37106
HWMon.GPU.#1...:  0% Util, 47c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (40 secs)
Speed.GPU.#1...:        0 H/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 12622270
Rejected.......: 39358
HWMon.GPU.#1...:  0% Util, 48c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (50 secs)
Speed.GPU.#1...:        0 H/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 15770541
Rejected.......: 41901
HWMon.GPU.#1...:  0% Util, 48c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (1 min, 0 secs)
Speed.GPU.#1...:        0 H/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 18916560
Rejected.......: 42192
HWMon.GPU.#1...:  0% Util, 50c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (1 min, 11 secs)
Speed.GPU.#1...:        0 H/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 22062452
Rejected.......: 42356
HWMon.GPU.#1...:  0% Util, 51c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (1 min, 21 secs)
Speed.GPU.#1...:        0 H/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 25208354
Rejected.......: 42530
HWMon.GPU.#1...:  0% Util, 52c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (1 min, 31 secs)
Speed.GPU.#1...:   336.7 kH/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 31499982
Rejected.......: 42702
HWMon.GPU.#1...:  0% Util, 53c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Running
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (1 min, 41 secs)
Speed.GPU.#1...:   340.0 kH/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 34645893
Rejected.......: 42885
HWMon.GPU.#1...:  0% Util, 53c Temp,  0rpm Fan


Session.Name...: cudaHashcat
Status.........: Exhausted
Input.Mode.....: Pipe
Hash.Target....: File (hash.txt)
Hash.Type......: MD5
Time.Started...: Wed Dec 02 22:10:10 2015 (1 min, 52 secs)
Speed.GPU.#1...:   330.6 kH/s
Recovered......: 0/845 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 38393920
Rejected.......: 43074
HWMon.GPU.#1...:  0% Util, 53c Temp,  0rpm Fan

Started: Wed Dec 02 22:10:10 2015
Stopped: Wed Dec 02 22:12:06 2015

Hum, what am I doing wrong ?

Thank you.

Windows 8 / GTX 980 / regedit patch applied.

[epixoip]

You're running a straight dictionary attack against a fast hash, so it is impossible to gain GPU acceleration as you do not have an amplifier. You then made an already-slow attack even slower by using pipe.

[Mem5]

OK, new try with :
- wordlist : 38M words (more than the 10M advised in the FAQ)
- [amplifier] rules list of 2000 rules applied on GPU (more than the 1000 advised in the FAQ)

Give :

- Straigh use of cudahashcat :
"ATTENTION! The wordlist or mask you are using is too small....."
Duration : 1 minute 10 seconds

- piping hashcat :
hashcat-cli64.exe --stdout *.dic | cudaHashcat64.exe -w 3 -r 2k.rule hash.txt
Duration : ~3 minutes

For fast hashes such as MD5, it is crucial to expand the candidates on the GPU with rules or masks in order to achieve full acceleration

It seems that I did what the FAQ advise, why can't I get full speed ?

For fast hashes, I would rather not using pipe, right ?

[epixoip]

It's a potential workaround, not a magic fix. Pipe incurs more host-device transfers and is more sensitive to PCI-e bus speed & latency.

You should be using cpu hashcat for this attack.

[Mem5]

It's a potential workaround, not a magic fix.

Ok, got it.

You should be using cpu hashcat for this attack.

Hum, Cpu Hashcat gives 33Mh/s while cudahashcat give 500Mh/s, so even with the message 'attention..' I would continue to use GPU

[Betawave]

It's a potential workaround, not a magic fix.

Ok, got it.

You should be using cpu hashcat for this attack.

Hum, Cpu Hashcat gives 33Mh/s while cudahashcat give 500Mh/s, so even with the message 'attention..' I would continue to use GPU

Calling experts:  Is the above true or is the rate an indicated rather than actual rate?  I've noticed the same thing in my limited testing and wondered why GPUs aren't used even for sub-optimal GPU tasks if they run through many more hashes than a CPU (albeit inefficiently).  Can anyone clarify?

[epixoip]

It depends on the hardware and the workload. There's no "one size fits all" answer, you just have to know your tools. In this case, it looks like Mem5 has a really underpowered CPU if he's only pulling 33 MH/s on MD5, so even an inefficient attack on GPU is faster in his case.

[Mem5]

Exactly, I use hashcat on a lowcost i3, and cudahashcat on a high-class GPU that's why my I would always prefer using GPU tools.