Posts: 19
Threads: 3
Joined: Jan 2013
Hi. I'm running w7 x64 with 13.04 catalist drivers.
My hardware:
1. radeon hd6670
2. radeon hd7970.
Cracking WPA handshakes.
1. hd7970 overheats. severely. i have crappy chassis, and gonna have to improve it's venting, but that's not the point. In some cases overheating can't be fixed easily. Program should deal with it. --help suggests only this for this matter:
--gpu-temp-abort=NUM
Abort the WHOLE process because of the ONE 7970 overheated ??? BTW 6670 works just fine, there's no need to stop it. There's no need to abort 7970 either. All you need is to wait for some time for 7970 to cooldown.
I believe, correct desision is to pause overheated device only. Something like --gpu-temp-protection=90,80 -- pause calculation on the device when it reaches 90 degrees, until it will cool down to 80 degrees - then resume calculations.
2. Running dictionary with big set of rules (don't really remember exactly rulename, but i believe it was d3ad0ne.rule or rockyou-30000.rule). 6670 usually performes around 27000keys per secons. plain dictionaries, bruteforce masks, simple rules - everything ok. With the big set of rules, hashcat shows 6670's speed around 2700 kps. about 10 times slower than usual. Second device (7970) works ok with it's usual speed.
3. hashcat does not recognizes hash-filename. In the bat-file, i have to add two garbage bytes before file name for hashcat to accept it:
set InputFile=%1.hccap
[...]
%ProgPath%\oclHashcat-plus64.exe -a 0 -m 2500 -p : --session=%InputFile% --username -o %ResultFilename% --outfile-format=3 -u 256 %TempControl% %GPU% T:%InputFile% %Dictionaries%
4. hashcat randomly hangs after completing with exhausted. I have to kill the process and then think how to resume calculation from the point where it hanged. Today it hanged THREE times in a row after completing exactly the same small dictionary.
5. key [b] means 100% hanging hashcat. tried several times to use this to bypass couple of completed dictionaries after hashcat hanged (see â„–4) and...
bypassing.
bypassing........................
and so on. had to kill it and edit dictionaries list to force it to go on to the next dictionaries
Wanted to say some more just can't remember now what  If remember, will add later.
Posts: 649
Threads: 18
Joined: Nov 2010
1. Overheating is your problem not ours. Maybe try underclocking it
2. Sounds like not enough work?
3. Unintended use, looks like you found a solution though
4. Fixed in beta, wait for release
5. Again, fixed in beta.
Posts: 19
Threads: 3
Joined: Jan 2013
1. --gpu-temp-abort=NUM - that IS your problem, and to do it CORRECTLY - is NOT ? )
let's imagine i won't be able to avoid overheating - what will i do then? To sit and press s s s s p s s s r s s s p s s s r s s s... ?
2. Funny. i5 2500K 3.3Ghz can't supply 150kps? In all the other cases it can with near 0% cpu-load.
Posts: 649
Threads: 18
Joined: Nov 2010
1. Yes, that works as intended. When you hit XC the program aborts.
2. I dont see how your cpu has anything to do with this? I am saying the gpu that is "slow" doesn't have enough work.
Posts: 19
Threads: 3
Joined: Jan 2013
10-03-2013, 02:31 AM
(This post was last modified: 10-03-2013, 02:35 AM by falcon111.)
1. If i had a laptop with mobility radeon, you'll advise me to improve it's venting too?
All i'm trying to say, hashcat already have --gpu-temp-retain=NUM option. You're checking GPU's temperature and trying to maintain on the same level by changing fan duty. That's great option. When cooling system manages the overheating successfully. But when cooling system does not work efficiently enough, all the hashcat can offer is ugly decision to abort all calculations.
I mean, you already know the GPU's temperature, and it's easy to throttle calculations on overheated GPU waiting for it to colldown, that's not hard to do it. I don't understand why you refuse to add such option.
2. Ok. I can see abnormally low kps on one gpu at the same time when second gpu works at full speed. It lasts for a whole period of dictionary+rule calculation. I consider it's a bug, and i've told you so.
Posts: 649
Threads: 18
Joined: Nov 2010
If you were using a laptop I would advise that you didnt use it because laptops are not meant to be used like that. You keep trying to pin your poor build choices on things that really arent in our control anyway. You cannot simply throttle calculations like you appear to think. The reason things work this way now is because the bios will start stepping the clocks down until they eventually reach next to nothing. The sane thing to do was to put an abort switch in so that if you hit the thermal limit specified it would stop before the bios took over.
Posts: 19
Threads: 3
Joined: Jan 2013
2. GPU 1 == radeon 6670, GPU 2 == radeon 7970 downclocked to 500Mhz
Normal conditions 1:
Code: [s]tatus [p]ause [r]esume [b]ypass [q]uit =>
Session.Name...: 10.hccap
Status.........: Running
Input.Mode.....: Mask (?d?d?d?d?d?d?d?d) [8]
Hash.Target....: Wi-Fi-333 (18:f4:6a:64:c9:cc <-> c8:3a:35:34:a5:b8)
Hash.Type......: WPA/WPA2
Time.Started...: Fri Oct 04 00:03:07 2013 (6 secs)
Time.Estimated.: Fri Oct 04 00:20:28 2013 (17 mins, 14 secs)
Speed.GPU.#1...: 26964 H/s
Speed.GPU.#2...: 73081 H/s
Speed.GPU.#*...: 100.0 kH/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 647168/100000000 (0.65%)
Rejected.......: 0/647168 (0.00%)
Speed.GPU.#1...: 26964 H/s
Normal conditions 2:
Code: [s]tatus [p]ause [r]esume [b]ypass [q]uit =>
Session.Name...: dasha.hccap
Status.........: Running
Rules.Type.....: File (J:\WiFi\Dict\Rules\Common_Additions.rule)
Input.Mode.....: File (J:\WiFi\Dict\Russian_Full.RusToEng.txt)
Hash.Target....: Dasha (00:26:5a:00:2a:56 <-> f8:d1:11:52:95:b4)
Hash.Type......: WPA/WPA2
Time.Started...: Thu Oct 03 21:45:02 2013 (2 hours, 30 mins)
Time.Estimated.: Fri Oct 04 00:48:09 2013 (32 mins, 21 secs)
Speed.GPU.#1...: 26856 H/s
Speed.GPU.#2...: 72979 H/s
Speed.GPU.#*...: 99835 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 385526161/577712466 (66.73%)
Rejected.......: 27603345/385526161 (7.16%)
Speed.GPU.#1...: 26856 H/s
Something strange 1:
Code: oclHashcat-plus v0.15 by atom starting...
Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 35377
Workload: 256 loops, 8 accel
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled
Device #1: Turks, 1024MB, 580Mhz, 6MCU
Device #2: Tahiti, 2048MB, 580Mhz, 32MCU
Device #1: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/m2500.Turks_1124.2_1124.2 (VM).kernel (588132 bytes)
Device #1: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/bzero.Turks_1124.2_1124.2 (VM).kernel (33864 bytes)
Device #2: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/m2500.Tahiti_1124.2_1124.2 (VM).kernel (313116 bytes)
Device #2: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/bzero.Tahiti_1124.2_1124.2 (VM).kernel (30456 bytes)
Cache-hit dictionary stats J:\WiFi\Dict\SureThing.txt: 4360 bytes, 625 words, 22110625 keyspace
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
Session.Name...: 11.hccap
Status.........: Running
Rules.Type.....: File (J:\WiFi\Dict\Rules\ocl\d3ad0ne.rule)
Input.Mode.....: File (J:\WiFi\Dict\SureThing.txt)
Hash.Target....: Wi-Fi-435 (4c:0f:6e:da:52:d9 <-> c8:60:00:72:18:e4)
Hash.Type......: WPA/WPA2
Time.Started...: Fri Oct 04 00:09:47 2013 (27 secs)
Time.Estimated.: Fri Oct 04 00:13:28 2013 (3 mins, 13 secs)
Speed.GPU.#1...: 2737 H/s
Speed.GPU.#2...: 73075 H/s
Speed.GPU.#*...: 75812 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 7606079/22110625 (34.40%)
Rejected.......: 5515387/7606079 (72.51%)
Session.Name...: 11.hccap
Status.........: Exhausted
Rules.Type.....: File (J:\WiFi\Dict\Rules\ocl\d3ad0ne.rule)
Input.Mode.....: File (J:\WiFi\Dict\SureThing.txt)
Hash.Target....: Wi-Fi-435 (4c:0f:6e:da:52:d9 <-> c8:60:00:72:18:e4)
Hash.Type......: WPA/WPA2
Time.Started...: Fri Oct 04 00:09:47 2013 (1 min, 19 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...: 2647 H/s
Speed.GPU.#2...: 72622 H/s
Speed.GPU.#*...: 75269 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 22110625/22110625 (100.00%)
Rejected.......: 16187573/22110625 (73.21%)
Speed.GPU.#1...: 2647 H/s
Something strange 2:
Code: oclHashcat-plus v0.15 by atom starting...
Hashes: 1 total, 1 unique salts, 1 unique digests
Bitmaps: 8 bits, 256 entries, 0x000000ff mask, 1024 bytes
Rules: 30000
Workload: 256 loops, 8 accel
Watchdog: Temperature abort trigger disabled
Watchdog: Temperature retain trigger disabled
Device #1: Turks, 1024MB, 580Mhz, 6MCU
Device #2: Tahiti, 2048MB, 580Mhz, 32MCU
Device #1: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/m2500.Turks_1124.2_1124.2 (VM).kernel (588132 bytes)
Device #1: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/bzero.Turks_1124.2_1124.2 (VM).kernel (33864 bytes)
Device #2: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/m2500.Tahiti_1124.2_1124.2 (VM).kernel (313116 bytes)
Device #2: Kernel C:\Programs\oclHashCat\oclHashcat-plus/kernels/4098/bzero.Tahiti_1124.2_1124.2 (VM).kernel (30456 bytes)
Cache-hit dictionary stats J:\WiFi\Dict\SureThing.txt: 4360 bytes, 625 words, 18750000 keyspace
[s]tatus [p]ause [r]esume [b]ypass [q]uit =>
Session.Name...: 11.hccap
Status.........: Running
Rules.Type.....: File (J:\WiFi\Dict\Rules\ocl\rockyou-30000.rule)
Input.Mode.....: File (J:\WiFi\Dict\SureThing.txt)
Hash.Target....: Wi-Fi-435 (4c:0f:6e:da:52:d9 <-> c8:60:00:72:18:e4)
Hash.Type......: WPA/WPA2
Time.Started...: Fri Oct 04 00:07:57 2013 (17 secs)
Time.Estimated.: Fri Oct 04 00:11:48 2013 (3 mins, 33 secs)
Speed.GPU.#1...: 2738 H/s
Speed.GPU.#2...: 72782 H/s
Speed.GPU.#*...: 75520 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 2949710/18750000 (15.73%)
Rejected.......: 1657290/2949710 (56.18%)
Session.Name...: 11.hccap
Status.........: Exhausted
Rules.Type.....: File (J:\WiFi\Dict\Rules\ocl\rockyou-30000.rule)
Input.Mode.....: File (J:\WiFi\Dict\SureThing.txt)
Hash.Target....: Wi-Fi-435 (4c:0f:6e:da:52:d9 <-> c8:60:00:72:18:e4)
Hash.Type......: WPA/WPA2
Time.Started...: Fri Oct 04 00:07:57 2013 (1 min, 49 secs)
Time.Estimated.: 0 secs
Speed.GPU.#1...: 2657 H/s
Speed.GPU.#2...: 71557 H/s
Speed.GPU.#*...: 74213 H/s
Recovered......: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.......: 18750000/18750000 (100.00%)
Rejected.......: 10580692/18750000 (56.43%)
Speed.GPU.#1...: 2657 H/s
Is this a bug or what?
Posts: 649
Threads: 18
Joined: Nov 2010
The high rejected count might have something to do with the card under performing. It's possible that there isnt enough work being passed to it.
Posts: 19
Threads: 3
Joined: Jan 2013
When running on the only 6670 - it works with full speed on the same dictionary/rules. Reject count (short passwords) should skip bad passwords and go on with the next passwords. GPUs should work with full speed. In my example, summary calculction speed is ~75К/s. One 7970 not being downclocked gives more than a 130K with no problems, so i can't understand why hashcat can't load up 6670 gpu. WPA calculations are slow enough for supplying keys with 100% gpu load. So i can't understand why this is happening.
And i've remembered what i wanted to add
6. When running hashcat with --gpu-temp-retain=x parameter, it changed GPU fan speed to maintain temperature on the same level. But when i press 'q' to abort calculations, it locks fan duty on the last level and do not switching it back to "auto" mode. F.e. GPU temp is 82C, fan duty 100%, i'm interrupting hashcat and gpu's fan will maintain 100% duty, until i'll run catalist control center and will disable "enable manual fan control" in it.
Posts: 621
Threads: 57
Joined: May 2010
Also, the speed you are getting for the "Strange" examples are not accurate because you are already finished the attacks (100%). In your normal example, you are far from the end.
|
