Please note, this is a STATIC archive of website hashcat.net from 08 Oct 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: V56 is up
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
hey beta-testers,

v56 fixed a very evil bug that lead to total unpredictable other bugs. please do all your testing again Smile

--
atom
Tnx atom Smile in Barcelona atm but will be back in UK Friday so will do testing then.
Since after plus-0.09b45 up to plus-0.09b57, when I try:
Code:
hc64p -a3 --bf-min=8 --markov-disable --force 00000000000000000000000000000000 ?a?a?a?a?a?a?a?a
I get:
Code:
[s]tatus [p]ause [r]esume [b]ypass [q]uit => ERROR: cuMemcpyDtoD() 1
Try with b58 pls, just uploaded
b58 also fixed this for both amd and nvidia, pls verify:

Quote:- For -m 2711 vBulletin > v3.8.5, Nothing works
- For -m 2811 vBulletin > v3.8.5, Nothing works
Just tried -m2(6|7)11 on all lengths, all attack-modes. Result: All Works!
Also "cuMemcpyDtoD() 1" is gone! Thanks atom!
System:
Windows7 64-bit, nVidia, 304,79 beta, plus-0.09b58.

Testing is way much easier than I thought. Going to hit other hash-types!
System: Windows 7 64 bit, catalyst 12.8 HD5750, oclhashcat-plus beta 56

I did my usual test on all algos and all modes. I won't specify what is working since now it's almost everything. Also, all the crashes are fixed!

For -m 1710 sha512($pass.$salt), bruteforce of length 4 does not work. Everything else works.
For -m 2711 and -m 2811, the usual bug. Dictionary attack works but all other mode fails.

That's it. I will try to reproduce the -m 1710 bug again and report if I find something useful.

For the AMD side, v 0.09 is almost ready to go! I can't wait to test the Nvidia now (probably this evening).
Finally, all tests are done!
Results: (If no note is given means all is working perfectly!)
Code:
-m0
-m10
-m20
-m30
-m40
-m100
-m110
-m120
-m130: Same problem as -m131, -m132.
-m140
-m300
-m400
-m500: All works EXCEPT it fails to crack any 1-character-long password on all attack modes (Only -a0 and -a3 can get that though).
-m900
-m1000
-m1100
-m1400
-m1410
-m1420
-m1500
-m1600: Same problem as -m500.
-m1700
-m1710: Interestingly, None of -a1, -a6 and -a7 work, on all lengths.
-m1720
-m1800
-m2100
-m2400
-m2500: SKiPPiNG.
-m2600
-m3000: Worked well, But this BUG (https://hashcat.net/forum/thread-1216.html) still exists. Funny it's giving me different results this time, but still wrong results!
-m3100: I'm not sure about this algo, when I use -a3, all is being cracked but if len(pass) > 8 : its truncating the passes to 8. Other attacks don't do that, they act just like a regular MD5.
-m3200
-m11
-m21
-m101
-m111
-m112
-m121
-m122
-m131: All good, except -a7 seems to have a problem.
-m132: Exact same problem of -m131. Only 1-character-long password is found when doing -a7, which should never happen with -a7 (it works with a mask!).
-m141
-m1722
-m2611
-m2711
-m2811: MyBB1.2+ uses ?l?u?d_len(8) salt, please add an exception.
I'm keeping this one-damn-fine version =D

System: Windows7 64-bit, nVidia, 304,79 beta, plus-0.09b58.
Thanks to atom's perl code and my MasterHasher.php.
Thanks for the test results, very very very helpful. Indeed I focuses on amd mostly, but will not try to fix stuff on nvidia, too.

This bugfixing round was really neccessary Smile