Cryptohaze.com

Hi at all,

I played a little bit with the GRT. Now I created 3 Tables:

md5_mixalpha-numeric#8_0_200000x1676000000
md5_mixalpha-numeric#8_1_200000x1676000000
md5_mixalpha-numeric#8_2_200000x1676000000

My question is, which index should I use with the GRTIndexTables ?

How many bits of index?

Try different values until you get somewhere between 20 & 50 items per index. It's just a rough ballpark number.

Eagle_Fist wrote:md5_mixalpha-numeric#8_0_200000x1676000000
md5_mixalpha-numeric#8_1_200000x1676000000
md5_mixalpha-numeric#8_2_200000x1676000000

You should have the table index "-i / --tableindex" be something like 0, 200000, 400000, 600000

It's not as bad as I originally thought but you will have more duplicate passwords in different tables. Basically even and odd table indexes don't have problems with each other, but even and even or odd and odd do. Good news is they "break off" the merged chains because there is one in 256 characters that is different (assuming 256 is not dividable by the character set's length). There's a 3.08% chance (with 8 characters in a password) at every link that it will "break off" after chains have merged. So it is expected to "break off" after 22.14 links.

This is why newer tables are generated like this:
NTLM-idx0-chr95-cl200000-perfect.grt
NTLM-idx300000-chr95-cl200000-perfect.grt
NTLM-idx600000-chr95-cl200000-perfect.grt
NTLM-idx900000-chr95-cl200000-perfect.grt