Posts: 5,185
Threads: 230
Joined: Apr 2010
Fixed:
Quote:- For -m 10 md5($pass.$salt), Bruteforce of length 2 is not working.
- For -m 30 md5(unicode($pass).$salt), Length 2 does not work on bruteforce.
- For -m 110 sha1($pass.$salt), Bruteforce of length 2 is not working.
- For -m 112 Oracle 11g, Bruteforce of length 2 is not working. The rest is perfect.
- For -m 1410 sha256($pass.$salt), bruteforce with length 2 did not work. Everything else works fine.
Posts: 5,185
Threads: 230
Joined: Apr 2010
Fixed:
Quote:Prompt is not shown sometimes
Posts: 5,185
Threads: 230
Joined: Apr 2010
Left:
Quote:- For -m 30 md5(unicode($pass).$salt), Length 15 does not work on all modes
- For -m 111 nsldaps, SSHA-1(Base64), Netscape LDAP SSHA, Dictionary attack works (-a 0) but all the other attack mode fails.
- For -m 141 EPiServer 6.x, Nothing worked.
- For -m 1710 sha512($pass.$salt), dictionary worked for all length and bruteforce for length 8, 12 and 15. All the other test (mode + length) failed.
Posts: 5,185
Threads: 230
Joined: Apr 2010
Fixed:
Quote:- For -m 30 md5(unicode($pass).$salt), Length 15 does not work on all modes
Left:
Quote:- For -m 111 nsldaps, SSHA-1(Base64), Netscape LDAP SSHA, Dictionary attack works (-a 0) but all the other attack mode fails.
- For -m 141 EPiServer 6.x, Nothing worked.
- For -m 1710 sha512($pass.$salt), dictionary worked for all length and bruteforce for length 8, 12 and 15. All the other test (mode + length) failed.
Posts: 5,185
Threads: 230
Joined: Apr 2010
Fixed:
Quote:- For -m 111 nsldaps, SSHA-1(Base64), Netscape LDAP SSHA, Dictionary attack works (-a 0) but all the other attack mode fails.
- For -m 1710 sha512($pass.$salt), dictionary worked for all length and bruteforce for length 8, 12 and 15. All the other test (mode + length) failed.
Left:
Quote:- For -m 141 EPiServer 6.x, Nothing worked.
Posts: 5,185
Threads: 230
Joined: Apr 2010
I have uploaded a new beta b43, please retry everything (not just the stuff that was marked as buggy) because of bugfixes new errors can appear somewhere.
Posts: 621
Threads: 57
Joined: May 2010
(08-10-2012, 11:37 AM)atom Wrote: Can not reproduce:
Quote:- For -m 130 sha1(unicode($pass).$salt), attack mode 1 and 7 fails. Mode 0,3 and 6 works perfectly well.
- For -m 132 MSSQL(2005), attack mode 1 and 7 fails. Mode 0,3 and 6 works perfectly well.
- For -m 131 MSSQL(2000), something really wrong is happening. Only the password with length 4 was cracked normally with bruteforcing. The password of length 2 that was supposed to be cracked by bruteforcing was cracked by the following
command line in mode 7: cudahashcat-plus64.exe -a 7 -d 1 -m 131 -o found.txt hash.txt ?s?s dic1.txt -- I have double-checked, there is no empty line in dic1.txt so I don't know how it got cracked.
- For -m 1800 sha512crypt, SHA512(Unix), there is random problems. -a 1 for length 15 failed, -a 3 for length 4 failed, -a 6 for length 15 failed, -a 7 for length 4 and 8 failed. The rest worked.
- For -m 2100 DCC2, I have generated the length 15 hashes with PasswordsPro Hash generator and they were cracked in all mode... Dictionary mode for length 2 failed. Bruteforce for length 4 failed. All the rest worked.
I really tried all of them on my hd6990. very strange! For -m 130, I don't get the same problem on my HD5750 (on v42 only bruteforce of length 2 did not work) so it could be Nvidia specific.
For -m 131, I get pretty much the same thing on both platform. Maybe the hash generation is the culprite. I will try to re-generate them and retest on v44.
For -m 132, I don't get the same problem on my HD5750 (on v42 only bruteforce of length 2 did not work) so it could be Nvidia specific.
For -m 1800, It seems like both platform share the same problems but with all the AMD crashes, it's hard to compare. I will try to regenerate some of the hashes and retest on v44.
For -m 2100, I get the same thing on both platform but the bruteforce on AMD crashed so I don't know the exact outcome. Again, I will try to regenerate the hashes and retest on v44.
Posts: 621
Threads: 57
Joined: May 2010
08-12-2012, 03:22 AM
(This post was last modified: 08-12-2012, 03:53 AM by mastercracker.)
For -m 131, I confirm that hash generation was the main source of the problem. There are still bugs however that I will report on the thread of v44.
For -m 2100, I figured out the bug for the length 2 dictionary not being cracked. The hash generated by Atom's perl script was with a username of length 14. Without giving any error message, this hash that was part of a group of 25 hashes total was skipped and not included in the cracking. Generating another hash for the same password with a different user name worked properly.
Posts: 5,185
Threads: 230
Joined: Apr 2010
ok i will close this thread, lets continue on the v44
|
