For the last post, I have added a not corrected bug for -m 132 that I skipped by mistake. For the GTX470, I get exactly the same result except that the -m 3000 is fine. I will quickly re-test the GTX460 for the -m 3000 only.
GTX460 is still bad for -m 3000. If I was running a cracking session on a GPU, pause it and start a new cracking session on the same GPU, can it cause this kind of problems or it should still run normally?
Fixed
- For -m 0 MD5, bruteforce of length 2, 4 and 8 fails.
- For -m 30 md5(unicode($pass).$salt), bruteforce on length 2 and 4 fails.
- For -m 130 sha1(unicode($pass).$salt), bruteforce on length 2 and 4 fails.
- For -m 131 MSSQL(2000), bruteforce on length 2 and 4 fails.
- For -m 132 MSSQL(2005), bruteforce on length 2 and 4 fails.
- For -m 900 MD4, Bruteforce on length 2,4,8 fails.
- For -m 1000 NTLM, Bruteforce on length 2,4 and 8 fails.
Not fixed or improperly fixed
- For -m 900 MD4, Bruteforce on length 12 fails.
(08-14-2012, 01:55 PM)atom Wrote: [ -> ]fixed:
Quote:-m 11 broken
I did not do all algos on v47 as it takes a lot of time but I can confirm that everything works for -m 11 on my HD5750. Was there anything else changed in v47? Otherwise, I will wait the next beta to test all modes.
(08-14-2012, 06:20 PM)mastercracker Wrote: [ -> ]I did not do all algos on v47 as it takes a lot of time but I can confirm that everything works for -m 11 on my HD5750. Was there anything else changed in v47? Otherwise, I will wait the next beta to test all modes.
this was defenitive not working in v45. remember, if you use -m 11, you must use a salt of exact length 32
when you find some time, please redo all tests with v47, i am a bit confused now whats all fixed and whats still left.
at least two things i know that are not working:
- -m 1800 sometimes does not work, like this one:
echo -n 74828 | ./oclHashcat-plus64.bin -m 1800 '$6$6273353688125078$LJYp.Kv3vMITYZ76EORGcieiWTIAxKrtBU9sz6TXnEf15h5d7OsSg3rz9tP9Ya7Phd0HKU9dIKChMu69V8Drk0'
- -m 141 completly does not work
--
rest should be ok
(08-14-2012, 11:19 PM)atom Wrote: [ -> ]when you find some time, please redo all tests with v47, i am a bit confused now whats all fixed and whats still left.
at least two things i know that are not working:
- -m 1800 sometimes does not work, like this one:
echo -n 74828 | ./oclHashcat-plus64.bin -m 1800 '$6$6273353688125078$LJYp.Kv3vMITYZ76EORGcieiWTIAxKrtBU9sz6TXnEf15h5d7OsSg3rz9tP9Ya7Phd0HKU9dIKChMu69V8Drk0'
- -m 141 completly does not work
--
rest should be ok
Ok. I think that you misunderstood my message about -m 11. I was just saying that now on v47 it's fully working on AMD (and it was not working on v45). As a final note, I don't know what the exact problem was with -m 11 and what was the fix but in the real world, there are also Joomla with 16 characters salt. Ideally to crack those we would need either -m 10 or -m 11 to support them.
I will redo the tests anyway on v47 but unless you made more changes than only on -m 11, you can expect that what will fail will be what I reported in my last posts as not fixed or improperly fixed and what you did not fix from the first post. When I will have the results on V47, I will start a new thread with everything for clarity. Do you prefer 1 thread for both Nvidia and AMD or 2 separate thread?
Quote:As a final note, I don't know what the exact problem was with -m 11 and what was the fix but in the real world, there are also Joomla with 16 characters salt. Ideally to crack those we would need either -m 10 or -m 11 to support them.
right. both 16 and 32 should work with -m 11, but you can also use the generic algorithm -m 10. that all should work
Quote:When I will have the results on V47, I will start a new thread with everything for clarity. Do you prefer 1 thread for both Nvidia and AMD or 2 separate thread?
1 thread for each, its easier to track