08-14-2012, 03:46 AM
(This post was last modified: 08-14-2012, 01:58 PM by mastercracker.)
READ BOTTOM FIRST
System: Windows 7 64 bit, Driver 285.62 GTX460, oclhashcat-plus beta 45
Corrected bugs:
-m 30 is now perfect.
-m 130 bruteforce of length 4 is fixed.
-m 131 Bruteforce on length 2 and 4
Not corrected or corrected improperly:
-m 130 sha1(unicode($pass).$salt), -a 1 for all length and -a 7 for all length failed.
-m 131 -a 1 and -a 7 for all length failed.
-m 132 -a 1 and -a 7 for all length failed.
-m 900 Bruteforce on length 12 failed.
New bug:
-m 3000 got screwed up somehow. Here's what was expected:
144c77b47ef6caf5:mc
43154416d62f6c2a:hash
85fa793a454d9840:qz
1a6b659a23a5b345:ToDo
e85d0c49cfb378e0:%*
2a5d8ece29452fb1:P0$7
a9c3248d86ab3ded:q!
310726e22190782c:T0Be
fff79def78d18000:$D
87203beb6f07d882:($$)
Here's the output:
144c77b47ef6caf5:MC <-- Ok
43154416d62f6c2a:HASH <-- ok
1a6b659a23a5b345:MCDO <-- There is a little bit of McDonalds in everyone...
e85d0c49cfb378e0:% <-- Not good
2a5d8ece29452fb1:P5 6 <-- Not good
1a6b659a23a5b345:MCDO <-- Not good
fff79def78d18000:*D <-- Not good
87203beb6f07d882:#%$) <-- Not good
The duplicate comes from the fact that everything is uppercased and my attacks are case sensitive but the wrong passwords created are bad. Also if it helps tracking, the expected results are in this order: length2 and length4 for -a 0 then -a 1 then -a 3, -a 6, -a 7.
UH OH. I DON'T KNOW IF YOU HAVE CORRECTED EVERY KERNEL OR ONLY THE ONES SPECIFIC FOR GTX470. I DID NOT THINK MUCH AND DID THE TEST ON MY GTX460 THIS TIME. I WILL CHECK ON GTX470 NOW.
System: Windows 7 64 bit, Driver 285.62 GTX460, oclhashcat-plus beta 45
Corrected bugs:
-m 30 is now perfect.
-m 130 bruteforce of length 4 is fixed.
-m 131 Bruteforce on length 2 and 4
Not corrected or corrected improperly:
-m 130 sha1(unicode($pass).$salt), -a 1 for all length and -a 7 for all length failed.
-m 131 -a 1 and -a 7 for all length failed.
-m 132 -a 1 and -a 7 for all length failed.
-m 900 Bruteforce on length 12 failed.
New bug:
-m 3000 got screwed up somehow. Here's what was expected:
144c77b47ef6caf5:mc
43154416d62f6c2a:hash
85fa793a454d9840:qz
1a6b659a23a5b345:ToDo
e85d0c49cfb378e0:%*
2a5d8ece29452fb1:P0$7
a9c3248d86ab3ded:q!
310726e22190782c:T0Be
fff79def78d18000:$D
87203beb6f07d882:($$)
Here's the output:
144c77b47ef6caf5:MC <-- Ok
43154416d62f6c2a:HASH <-- ok
1a6b659a23a5b345:MCDO <-- There is a little bit of McDonalds in everyone...
e85d0c49cfb378e0:% <-- Not good
2a5d8ece29452fb1:P5 6 <-- Not good
1a6b659a23a5b345:MCDO <-- Not good
fff79def78d18000:*D <-- Not good
87203beb6f07d882:#%$) <-- Not good
The duplicate comes from the fact that everything is uppercased and my attacks are case sensitive but the wrong passwords created are bad. Also if it helps tracking, the expected results are in this order: length2 and length4 for -a 0 then -a 1 then -a 3, -a 6, -a 7.
UH OH. I DON'T KNOW IF YOU HAVE CORRECTED EVERY KERNEL OR ONLY THE ONES SPECIFIC FOR GTX470. I DID NOT THINK MUCH AND DID THE TEST ON MY GTX460 THIS TIME. I WILL CHECK ON GTX470 NOW.