howto use stats processor with oclHashcat+ v0.8?

[ntk]

thank you Hash-IT.

With sudo I am able to run the command. But when the status screen comes up, as you can see in the trace log, then system stops calculation and cant find the simple password. Basically I run several experiments with stdin. I feed in from larger key space then reduce small, and exactly one key.


./mp64.bin -1 abcd?d ?1?1?1?1?1?1?1?1 | ... (not found; automatic status screen)
./mp64.bin -1 ?d ?1?1?1?1?1?1?1?1 | ... (not found; automatic status screen)
./mp64.bin -1 ?d '1'?1?1?1?1?1?1?1 | ... (found; no automatic status screen)
echo '12345678' | ... (found; no automatic status screen)
Only with this mask it can find the password. What I can guess here is: Because there is too short time for status window to come up, system has not stop before it checked the key and produced result.

I am aware of the internal generation of oclHashcat+ via command:
sudo ./oclHashcat-plus64.bin -m 2500 Harkonen.hccap -o foundharkonen.txt -1 ?d ?1?1?1?1?1?1?1?1
But it is not about finding the key. It is about stdin, I need it for certain purpose.

My question are:
1. why when I feed in large amount of combinations the status window comes up without my involvement?
2. does it happen on other linux system, or window when you use combination like this.
3. why when status screen comes up GPU load immediately goes down to NULL. system stop working, i.e not find this simple password
4 How can I produce some traces for Atom to check this STDIN behaviour.
5 do you use stdin, in different command format?does it work long hours?
6 if you can use sp64.bin as replacement for BF, how do you pipe in oclHashcat+

[atom]

1. why when I feed in large amount of combinations the status window comes up without my involvement?

because it always does each 10 seconds or so plus when its finished as a form of final status. this is required in stdin mode since the program gets the data via stdin. so there is no way for the program to read the keypress from stdin.

2. does it happen on other linux system, or window when you use combination like this.

its not dependant on the input (notice the final status)

3. why when status screen comes up GPU load immediately goes down to NULL. system stop working, i.e not find this simple password

typical driver problem. use cat 12.6

4 How can I produce some traces for Atom to check this STDIN behaviour.

i dont think its a bug. i think its some problem with driver, or maybe with the hccap.

5 do you use stdin, in different command format?does it work long hours?

the way you did it is correct.

6 if you can use sp64.bin as replacement for BF, how do you pipe in oclHashcat+

same way, just try it

[ntk]

1. why when I feed in large amount of combinations the status window comes up without my involvement?

because it always does each 10 seconds or so plus when its finished as a form of final status. this is required in stdin mode since the program gets the data via stdin. so there is no way for the program to read the keypress from stdin.

at least I know that is not my fault to activate the status screen.

2. does it happen on other linux system, or window when you use combination like this.

its not dependant on the input (notice the final status)

3. why when status screen comes up GPU load immediately goes down to NULL. system stop working, i.e not find this simple password

typical driver problem. use cat 12.6

I am reluctant to take your advise here with 12.6 because it won't solve this problem. Firstly I had use 12.6. It has bad performance even on pyrit so I go back to 12.4. Secondly I have read posts from 3 users on this forum, reporting seemingly various problems but I could make reduction & see this 'stop calculation' every where, If you have trace in the code, we can activate debug and show it.

in a sec SP64 -pw-min 8 ?d?d?d?d?d?d?d?d produce a file of 900MB large dict, it cant be not enough data for oclHashcat+

4 How can I produce some traces for Atom to check this STDIN behaviour.

i dont think its a bug. i think its some problem with driver, or maybe with the hccap.

Hakonen is a standard example, aircrack-ng can solve it, pyrit can solve it, ochHashcat-plus can solve it with direct generation of combinations. it s not problem with the cap or hccap Atom.

let experiment and see failed with stdin, then run ocl with direct mask processor
./oclHashcat-plus64.bin Hakonen.hccap -o foundhakonen.txt ?d?d?d?d?d?d?d?d
you see it pass.
run again with stdin to see it fails, do again with ocl with direct mask processor to see it pass
run again with stdin to see it fails, do again with ocl with direct mask processor to see it pass
run again with stdin to see it fails, do again with ocl with direct mask processor to see it pass

Consistently ===> that is a problem hang with stdin

5 do you use stdin, in different command format?does it work long hours?

the way you did it is correct.

stdin is very important to me. If possible I would be obliged to run stdin-regression test for you in every release, but please do maintain and opt to optimize it too, even when you'd have completed Markov's implementation into oclHashcat-plus

6 if you can use sp64.bin as replacement for BF, how do you pipe in oclHashcat+

same way, just try it

try it and see it fail.
run again with stdin to see it fails, do again with ocl with direct mask processor to see it pass
do three more time
Consistently ===>reduction ===> that is a problem hang with stdin

is it possible that we all have the debug version SW, we only need to activate the trace, Atom?

---

thank for you reply Atom.

[atom]

something is wrong with your system. cracked fine with your command:

root@sf:~/oclHashcat# /root/maskprocessor-0.68/mp64.bin -1 ?d ?1?1?1?1?1?1?1?1 | ./oclHashcat-plus64.bin -m 2500 x.hccap
oclHashcat-plus v0.09 by atom starting...

Password lengths: 8 min, 15 max
Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 1
Workload: 16 loops, 16 accel
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 80c
Device #1: Cayman, 1024MB, 830Mhz, 24MCU
Device #2: Cayman, 1024MB, 830Mhz, 24MCU
Device #1: Allocating 28MB host-memory
Device #1: Kernel ./kernels/4098/m2500.Cayman_938.1_1.4.1741.kernel (2087576 bytes)
Device #2: Allocating 28MB host-memory
Device #2: Kernel ./kernels/4098/m2500.Cayman_938.1_1.4.1741.kernel (2087576 bytes)

Starting attack in stdin mode...

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 10 secs
Time.Util....: 10001.6ms/258.7ms Real/CPU, 2.7% idle
Speed........: 157.3k c/s Real, 171.0k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 1572864
Rejected.....: 0
HWMon.GPU.#1.: 96% Util, 71c Temp, 98% Fan
HWMon.GPU.#2.: 96% Util, 69c Temp, N/A Fan

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 20 secs
Time.Util....: 20007.6ms/507.3ms Real/CPU, 2.6% idle
Speed........: 162.1k c/s Real, 170.9k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 3244032
Rejected.....: 0
HWMon.GPU.#1.: 96% Util, 72c Temp, 100% Fan
HWMon.GPU.#2.: 96% Util, 70c Temp, N/A Fan

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 30 secs
Time.Util....: 30013.4ms/765.7ms Real/CPU, 2.6% idle
Speed........: 163.8k c/s Real, 170.9k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 4915200
Rejected.....: 0
HWMon.GPU.#1.: 96% Util, 73c Temp, 100% Fan
HWMon.GPU.#2.: 96% Util, 70c Temp, N/A Fan

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 40 secs
Time.Util....: 40019.1ms/1010.3ms Real/CPU, 2.6% idle
Speed........: 164.6k c/s Real, 171.1k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 6586368
Rejected.....: 0
HWMon.GPU.#1.: 96% Util, 74c Temp, 100% Fan
HWMon.GPU.#2.: 96% Util, 70c Temp, N/A Fan

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 50 secs
Time.Util....: 50025.2ms/1254.2ms Real/CPU, 2.6% idle
Speed........: 165.1k c/s Real, 171.0k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 8257536
Rejected.....: 0
HWMon.GPU.#1.: 96% Util, 74c Temp, 100% Fan
HWMon.GPU.#2.: 96% Util, 71c Temp, N/A Fan

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 1 min, 0 secs
Time.Util....: 60031.0ms/1497.1ms Real/CPU, 2.6% idle
Speed........: 165.4k c/s Real, 170.8k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 9928704
Rejected.....: 0
HWMon.GPU.#1.: 95% Util, 74c Temp, 100% Fan
HWMon.GPU.#2.: 95% Util, 72c Temp, N/A Fan

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 1 min, 10 secs
Time.Util....: 70036.7ms/1747.7ms Real/CPU, 2.6% idle
Speed........: 165.6k c/s Real, 170.8k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 11599872
Rejected.....: 0
HWMon.GPU.#1.: 96% Util, 75c Temp, 100% Fan
HWMon.GPU.#2.: 95% Util, 71c Temp, N/A Fan

Harkonen:12345678

Status.......: Cracked
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 1 min, 15 secs
Time.Util....: 75046.7ms/1845.8ms Real/CPU, 2.5% idle
Speed........: 165.0k c/s Real, 170.7k c/s GPU
Recovered....: 1/1 Digests, 1/1 Salts
Progress.....: 12386304
Rejected.....: 0
HWMon.GPU.#1.: 88% Util, 70c Temp, 100% Fan
HWMon.GPU.#2.: 88% Util, 66c Temp, N/A Fan

Started: Sun Jul 15 12:00:56 2012

maybe you did not wpaclean it? pyrit does that automatically.

[ntk]

Thank you very much to have spent a lot of you valuable time to this problem. At least I know that 0.09 will not drive me crazy with stdin.

You have 0.09 I have 0.08 that could be the reason why it works on your system, and on some beta testers system, but not on mine.

Would it be possible for you to run a quicktest with 0.08 for me please. If you pass, I will wipe out my system and reinstall everything new. I realise too that you don't use sudo infront of ./oclHashcat-plus64.bin. In my system I have system complain about hashcat.pot file not permissible. Which linux are you using? It looks like Backtrack because of "root@sf:~/oclHashcat#", is it right?

I believe it is not because I have not performed wpaclean on the trace, Atom. We use both the same example cap "wpa2.eapol.cap" or called "Harkonen.cap", to generate hccap correct? Also if the Harkonen.cap was not cleaned with wpaclean, is really an issue, then oclHashcat-plus with direct generate combination won't be able to crack it in my current system too. But It does cracked it..

Only when I want to use MP64.bin (or sp64.bin) and oclHashcat+ in stdin mode, only then it show the strange status creen behaviour, oclHashcat+ stops responding, but the terminal which oclHashcat+ runs on, does not freeze, and it does not find password, as if it stops calculation when search time is longer the 10 sec.

Also I must stress that if I use mp64.bin with mask '12'?d?d?d?d?d?d, then oclHashcat+ in stdin mode cracks the password. SO the Harkonen.hccap must be a clean cap file.

[ntk]

@Atom
found already the answer of your operating system Ubuntu 12.04

and you run sudo su

[atom]

0.08 works fine, too:

root@sf:~/xy/oclHashcat-plus-0.08# /root/maskprocessor-0.68/mp64.bin -1 ?d ?1?1?1?1?1?1?1?1 | sudo ./oclHashcat-plus64.bin -m 2500 x.hccap
oclHashcat-plus v0.08 by atom starting...

Hashes: 1
Unique salts: 1
Unique digests: 1
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 1
GPU-Loops: 128
GPU-Accel: 16
Password lengths range: 8 - 15
Platform: AMD compatible platform found
Watchdog: Temperature limit set to 90c
Device #1: Cayman, 2048MB, 0Mhz, 24MCU
Device #2: Cayman, 2048MB, 0Mhz, 24MCU
Device #1: Allocating 28MB host-memory
Device #1: Kernel ./kernels/4098/m2500.Cayman.64.kernel (1646416 bytes)
Device #2: Allocating 28MB host-memory
Device #2: Kernel ./kernels/4098/m2500.Cayman.64.kernel (1646416 bytes)

Starting attack in wordlist stdin mode...

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 10 secs
Time.Util....: 10001.5ms/254.1ms Real/CPU, 2.6% idle
Speed........: 167.1k c/s Real, 178.2k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 1671168
Rejected.....: 0
HW.Monitor.#1: 96% GPU, 59c Temp
HW.Monitor.#2: 96% GPU, 61c Temp

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 20 secs
Time.Util....: 20005.5ms/503.1ms Real/CPU, 2.6% idle
Speed........: 172.0k c/s Real, 178.3k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 3440640
Rejected.....: 0
HW.Monitor.#1: 96% GPU, 62c Temp
HW.Monitor.#2: 96% GPU, 63c Temp

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 30 secs
Time.Util....: 30009.4ms/745.6ms Real/CPU, 2.5% idle
Speed........: 173.6k c/s Real, 178.0k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 5210112
Rejected.....: 0
HW.Monitor.#1: 96% GPU, 65c Temp
HW.Monitor.#2: 96% GPU, 66c Temp

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 40 secs
Time.Util....: 40012.3ms/983.4ms Real/CPU, 2.5% idle
Speed........: 172.0k c/s Real, 178.4k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 6881280
Rejected.....: 0
HW.Monitor.#1: 96% GPU, 68c Temp
HW.Monitor.#2: 96% GPU, 68c Temp

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 50 secs
Time.Util....: 50016.2ms/1231.1ms Real/CPU, 2.5% idle
Speed........: 173.0k c/s Real, 178.2k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 8650752
Rejected.....: 0
HW.Monitor.#1: 96% GPU, 69c Temp
HW.Monitor.#2: 96% GPU, 69c Temp

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 1 min, 0 secs
Time.Util....: 60020.1ms/1488.2ms Real/CPU, 2.5% idle
Speed........: 173.6k c/s Real, 178.2k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 10420224
Rejected.....: 0
HW.Monitor.#1: 96% GPU, 70c Temp
HW.Monitor.#2: 96% GPU, 70c Temp

Status.......: Running
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 1 min, 10 secs
Time.Util....: 70024.0ms/1723.7ms Real/CPU, 2.5% idle
Speed........: 172.7k c/s Real, 177.9k c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 12091392
Rejected.....: 0
HW.Monitor.#1: 96% GPU, 72c Temp
HW.Monitor.#2: 96% GPU, 72c Temp

Harkonen:12345678

Status.......: Cracked
Input.Mode...: Pipe
Hash.Target..: Harkonen (00:13:46:fe:32:0c <-> 00:14:6c:7e:40:80)
Hash.Type....: WPA/WPA2
Time.Running.: 1 min, 12 secs
Time.Util....: 72035.1ms/1755.7ms Real/CPU, 2.5% idle
Speed........: 171.9k c/s Real, 177.7k c/s GPU
Recovered....: 1/1 Digests, 1/1 Salts
Progress.....: 12386304
Rejected.....: 0
HW.Monitor.#1: 90% GPU, 68c Temp
HW.Monitor.#2: 90% GPU, 67c Temp

Started: Mon Jul 16 10:12:32 2012
Stopped: Mon Jul 16 10:13:44 2012

[ntk]

thank you Atom. I am convinced now.

---

please close this thread. there is no bug. that is only my system. Thank you.