![]() |
|
|
|
#1
|
|||
|
|||
|
Yeah, I am aware of the file sizes that one would have to encounter and this link that i had mentioed earlier, has plugins for various other hash algorithm too.
Also the precomputation time is just too large. even for a seven character alphanumeric password is 200+ days and file size of around 20gb. But what i wanted to ask is that, is it worth the effort for even 7 char password. the reason why i am asking this is that often people have observed collisions in these hash algorithms (reference hxxp://www.cryptool.de/). Keeping these too in mind, would it be helpful while patching codes, in which the files itself are checked for modifications while using these algorithms, like it was done for crc ? |
|
#2
|
|||
|
|||
|
a seven character password would be pie to bruteforce, on my machine it takes about 30min with alpha-num. Getting up into 8+ is where it gets long tho.
I think you should recheck your information, because here is a person that has actually accomplished it and you can submit ones for cracking :http://sarcaprj.wayreth.eu.org/ his NTLM hashes use upper/lower alpha-num-15 symbols and are only 18gb (and for sale!) Quote:
![]() I really wish someone would overhaul the rainbow crack app, like adding more algorithms, compression, and optimizations. |
|
#3
|
|||
|
|||
|
No such thing as 8 char passwords in NT. They are divided into two 7 char parts, which will be cracked individually.
|
|
#4
|
|||
|
|||
|
but dont Rainbow crack also offer plugins from MD2, MD4 and RIPEMD160 in addition to NTLM.
Maybe we could have a independant developement for more hash algorithms. |
|
#5
|
|||
|
|||
|
Rainbow crack algorithm
Quote:
hxxp://www.antsight.com/zsl/rainbowcrack/ search the page for 'Download' Enjoy
|
|
#6
|
|||
|
|||
|
tbone, I don't know if you accounted for this in your calculations.
Also, this explanation might be useful for the casual reader: Not all hashes are actually stored in the precomputed tables. For each "initial password", its hash is computed. Then the hash itself is taken as a new password (I think it's adjusted for the valid input chars) and a new hash calculated. This process repeats a number of times until you have a final hash. The only thing you store in the table files is the initial and final hash for each of these "chains", which reduces most of the space required. Still you'll end up with 20Gb of data; just imagine all hashes being stored When cracking, the known hash is transformed with the above process to obtain a list of hashes to form a new chain of the same length as the others. If one of these hashes matches the final hash of any of the stored tables, you have found the chain where it belongs. Then you just have to find the previous hash that chain - that is the password you're seeking
|
|
#7
|
|||
|
|||
|
Thankfully to crack passwords on a windows computer you only have to generate tables with 7 max length characters otherwise it would take forever.
Also there is also a mod for it to allow for computation of MySQL and Cisco PIX Hashes on oxit.it. You can also download a graphical interface if you care to. There I managed to contribute something
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|