System: Windows 7 64 bit, Driver 285.62 GTX470, oclhashcat-plus beta 44
Initial setup:
I am testing 5 different length of passwords (2,4,8,12,15) on attack mode 0,1,3,6 and 7. All that for each algo supported except WPA. There are 2 special cases: 1) -m 1500 DES(unix) where I do only length 2,4 and 8. 2) -m 3000 LM where I do only length 2 and 4.
The good
Here's the algos where everything is perfect: 0, 10, 20, 21, 40, 100, 101, 110, 111, 112, 120, 121, 122, 140, 300, 400, 500, 1000, 1100, 1400, 1410, 1420, 1500, 1600, 1700, 1720, 1722, 2400, 2600, 2611, 3000, 3100, 3200
The bad
- For -m 1710 sha512($pass.$salt), -a 1, -a 6 and -a 7 are not working. -a 0 and -a 3 works perfecty.
- For -m 1800 sha512crypt, SHA512(Unix), length 15 failed for -a 1 and -a 6. Length 4 failed for -a 3 and -a 7. Length 8 failed for -a 7. The remainder worked.
Edit: bruteforce from Length 4 resulted in the cuStreamSynchronize() 999 error after 5.68% progress.
- For -m 2100, Domain Cached Credentials2, mscash2, the username length 14 bug reported for AMD is also there for Nvidia. For bruteforcing of length 4, I get the cuStreamSynchronize() 999 error after 15.04% progress.
- For -m 2711 vBulletin > v3.8.5, only dictionary mode works. The rest fails.
- For -m 2811 IPB2+, MyBB1.2+, only dictionary mode works. The rest fails.
Notes
- I would still like the accepted salt length of -m 2811 to be extended to 8 characters.
- The cuStreamSynchronize() 999 error seems to match some attacks where I get driver crash with AMD. My GTX 470 has 1280 Mb of DDR5 memory.
Initial setup:
I am testing 5 different length of passwords (2,4,8,12,15) on attack mode 0,1,3,6 and 7. All that for each algo supported except WPA. There are 2 special cases: 1) -m 1500 DES(unix) where I do only length 2,4 and 8. 2) -m 3000 LM where I do only length 2 and 4.
The good
Here's the algos where everything is perfect: 0, 10, 20, 21, 40, 100, 101, 110, 111, 112, 120, 121, 122, 140, 300, 400, 500, 1000, 1100, 1400, 1410, 1420, 1500, 1600, 1700, 1720, 1722, 2400, 2600, 2611, 3000, 3100, 3200
The bad
- For -m 1710 sha512($pass.$salt), -a 1, -a 6 and -a 7 are not working. -a 0 and -a 3 works perfecty.
- For -m 1800 sha512crypt, SHA512(Unix), length 15 failed for -a 1 and -a 6. Length 4 failed for -a 3 and -a 7. Length 8 failed for -a 7. The remainder worked.
Edit: bruteforce from Length 4 resulted in the cuStreamSynchronize() 999 error after 5.68% progress.
- For -m 2100, Domain Cached Credentials2, mscash2, the username length 14 bug reported for AMD is also there for Nvidia. For bruteforcing of length 4, I get the cuStreamSynchronize() 999 error after 15.04% progress.
- For -m 2711 vBulletin > v3.8.5, only dictionary mode works. The rest fails.
- For -m 2811 IPB2+, MyBB1.2+, only dictionary mode works. The rest fails.
Notes
- I would still like the accepted salt length of -m 2811 to be extended to 8 characters.
- The cuStreamSynchronize() 999 error seems to match some attacks where I get driver crash with AMD. My GTX 470 has 1280 Mb of DDR5 memory.
(08-10-2012, 10:41 PM)atom Wrote: overall:I am not sure what the definition of "broken" is but for sure, 1400, 1410, 1420, 2600, 2611 are not broken in my setup. My only concern is my forceware that is not recent. I will do the tests on my 3rd computer and report if the problems are different.
-m 141 broken
-m 1800 broken (amd tested, nv not yet) on pw length 1 and 3
multihash (singlehash worked!), tested in -a 0
-m 2600 broken (amd tested, nv not yet)
-m 2611 broken (amd tested, nv not yet)
-m 2711 broken (amd tested, nv not yet)
-m 2811 broken (amd tested, nv not yet)