why?
because i have many friends that have web sites based on SQL. So because I'm a lazy person, and i hate to waste my time with bruteforcers, i would love some mysql tables
to begin mysql323_numeric#1-12 would be lovely
don't know if the client supports mysql generation...

cheers and thx for any answers
(again excuse my English...)

well a num 1-12 could be generated quite fast i think.
drop pb a pm and if your lucky he'll add it to the list.

i'm currently generating numeric 1-10 2500x6553600 7 tables...
i'll pm him later... or he can leave a reply here
config :


mysql323_numeric_1-10_0_2500x6553600_oxid#000.rar
mysql323_numeric_1-10_1_2500x6553600_oxid#000.rar
mysql323_numeric#1-10_2_2500x6553600_oxid#000.rar
mysql323_numeric_1-10_3_2500x6553600_oxid_000.rar
mysql323_numeric_1-10_4_2500x6553600_oxid#000.rar
mysql323_numeric_1-10_5_2500x6553600_oxid#000.rar
mysql323_numeric_1-10_6_2500x6553600_oxid_000.rar
mysql323_numeric#1-10_0_2500x3769576_[p]_.rar
mysql323_numeric#1-10_1_2500x3773175_[p]_.rar
mysql323_numeric#1-10_2_2500x3771764_[p]_.rar
mysql323_numeric_1-10_3_2500x3772603_[p]_.rar
mysql323_numeric_1-10_4_2500x3773303_[p]_.rt
mysql323_numeric_1-10_5_2500x3772874_[p]_.rar
mysql323_numeric_1-10_6_2500x3772603_[p]_.rar

alternative : 10 mirrors
mysql323_numeric#1-10_0_2500x3769576_[p]_.rar
mysql323_numeric#1-10_1_2500x3773175_[p]_.rar
mysql323_numeric#1-10_2_2500x3771764_[p]_.rar

thx the_drag0n for finishing the tables

alternative download http://drag0n.de/rts/

btw do you know if there is an 64bit version of winrtgen?

request : if you need mysql tables, please post a reply.

@the_drag0n : don't know.

sorry for double posting.
all the tables i'm creating are ment to fit a CD/DVD.
pls if you have a better config, post it !
after i finish creating the numeric tables, i'm going to make these :

if you want you can help

i could generate those numeric tables in 10.7 hours on one core

but i would be more interested in sha1 tables, and than pix, than mysql :p
and i think it would be far more useful if we generated some of those basic tables for these algorithms within the distrt project, as we have a LOT of CPU power available

i'm currently working on the ALL LM charset again btw;)

That's good to hear

Sorry for hijacking the thread. I know there are always some people who can really need some tables for the more seldomly used hashes. I'd still prefer some localized tables for the most common ones though. At the moment we wouldn't even be able to find a simple lowercase password which uses German umlauts oder Danish or French special characters. The only table I know that uses a few of those specials chars is the expensive OPHCrack table.

Here it's a common practice: Don't want your easy password cracked with a table ? Use an umlaut. So with a customized charset you might be able to bruteforce a word like "spüle", but you'll never find it with any of the tables. I think that's a huge drawback of the currently available tables - not only from the FRT project.

So what you suggest is tables with charsets just targeted for specific languages:

eg danish, german, swedish etc.

What kind of tables should that be?
Do you want to remake the tables below, once for every language * 2 (md5 + ntlm)?
mixalpha-numeric-all-space_1-6
loweralpha-space_1-9
loweralpha-numeric-space_1-8
mixalpha-numeric-space_1-7
loweralpha-numeric-symbol32-space_1-7

Or do you rather wan't to generate tables to crack longer english character passwords? (higher keyspace tables)

Hi PB,

that really depends on the computing power of the project.

Of course I'd love to see the tables you mentioned in localized versions. But recalculating all the tables again will certainly take up a huge amount of space and CPU for a while. I don't know if that would be ok for all our American and UK friends here. On the other hand the localized table(s) would always contain the "normal" English passwords as well, so even a user from UK or USA could use them without a big drawback. Maybe it's also possible to create two hybrid tables (MD5 + NTLM) for each language. Or one could include all the special chars of the most popular languages into ONE table. Why create one table that contains ä,ö,ü, one table that contains è,é,á,à and one table that contains Danish and one that contains Finnish, and so on when every table mostly contains the same ? I'm not sure though what the charset extension would mean for the size of the table. I personally could really use the tables you mentioned or a hybrid table made from those with German special chars.

I'd already be grateful for one or two of those tables. Trying to crack a hash with the mixalpha-numeric-space_1-7 and the mixalpha-numeric-all-space_1-6 table would certainly not find all of those hashes, but at least quite a few, I'd guess.

Actually that really depends what the FRT project is able to do. I don't want to block the CPU time for a table I personally like when nobody else has got a use for something like that.

1-7 or 1-6 tables are nearly useless.
a 1-8 alphanumspace + äöü uws would be great.

ok this is way offtopic
go and make a new topic !

There already is a topic, but thanks for the... erm... nice... hint...

second table is done

lm_all-space#1-7_0_10000
lm_all-space#1-7_1_10000
lm_all-space#1-7_2_10000
are all on their way to powerblade as we speak.
LM0 is 18.7GB
LM1 is 19.5GB
LM2 is 19.1GB
all have been perfected.