What do you the community suggest we do next?
Change to SHA1, MySQL323 or continue generating bigger MD5/NTLM set?

Remember this:
viewtopic.php?f=8&t=629&p=4675&hilit=what+others+thinks+about+us#p4675 ?

Should we generate the same set with a chainlength of 2000 and 4 indexes? Then we can crack the same hashes more than 50x faster than using their table. They use 250 indexes and we will only use 4 indexes.

Calculations shows that it has a keyspace of 70576641626495 and will take up 91 GB / table = 364 GB in total. (not indexed)
When indexed, it will be half the size, 182GB.

We could also increase the chainlength a bit more. It will increase the cracking time, but it will reduce the disksize and thus also reduce the disk loading time. Any suggestions? Voice your opinion!

MySQL323, SHA1, MySQLv5
small size sounds good, i don't care if the craking time increases.

That NTLM table you talks about, and MYSQL323

Whatever we go for next, I'd suggest to use a new charset, including the most common special characters like we discussed in another thread. Important for myself would be to include ä,ö,ü,Ä,Ö,Ü and ß. I don't know about the others, but I can remember that the guys from Oxid.it also added those plus some Danish characters.

The kind of tables to create should, in my opinion, depend on the length we need to create them. If it takes us a week to create some SHA1 and MYSQL tables to start with, then that's OK with me. After that we could start with MD5 and NTLM tables for larger passwords. However if the SHA1 and MYSQL tables would take us three months, then I'd rather create the MD5 and NTLM tables first.

id prefer generating sha1 tables.

Me too.

wpa i prefer ...
or ntlm

33 GB of WPA tables can already be downloaded from TBHOST.EU.

Maybe this helps.

don't think wpa tables are compatible with rcrack(i)

i prefer lm-frt

i would also like sha1.

wpa tables are quite usless, as they contain at least 8 chars, and they are salted with the routers bssid.
which means if you want to do wpa tables you'll have to make them specific for each router youre trying to attack.
if you use rtgen for wpa tables that is kinda like bruteforceing the wpa net.
you could also use cowpatty which was ment to be used for precomputing wpa "tables" but for that youd have to fully customize the client, which is right now quite useless as we are planning to write some new stuff maybe even start from scratch and dont have time for that.

we are OUT OF WORK!!!
how about starting a small sha1 RIGHT NOW (or as soon as you read this pb )

He must have read it, since my client received the first SHA parts

how about:
ntlm_hybrid(loweralpha#8-8,numeric#1-2)
md5_hybrid(loweralpha#8-8,numeric#1-2)

how about:
length 1-14 (or 8-14, since 1-8 is already done)
lm-ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789!@#$%^&*()-_+=~`[]{}|\:;"'<>,.?/

These are the most common characters for windoze passwords and predicted at 64GB using the original (unindexed) rainbowcrack http://www.antsight.com/zsl/rainbowcrack/

heres the original generation commands too
http://www.antsight.com/zsl/rainbowcrack/rtgen_cfg6.txt

Did you ever think about why you can NEVER find LM tables > 7 characters anywhere?