10-03-2013, 12:14 AM
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.
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.