What has happened to AtStake LC5 since Symantec brought it?

Lophtcrack is a program mostly used for network password auditing, as you probably already know.  It's also good for personal password discovery, and has some implications in hacking.  With LC5, i generated 100% probabilty alpha nuemeric tables that ran me 1GB, and took me 5 days to generate.  The longest search time, is roughly 7 days, but most usable passwords can be found in hours, or a day or two.  

Symantec intends to use @stake's software to package with their System's management software, among other things.  As we know it, lophtcrack will disappear.  The processes, and ideas behind it, will go into a module that will be placed into a Symantec suite.  And will probably get a new name.

If you're looking to buy it, it probably won't be anywhere, and you're only option would be obtain it illegally.  Which isn't hard mind you.  Or you could find one of it's sister products like Rainbow Crack, which is exactly like lophtcrack but without the brute force and hybrid functions.  Also, many of the rainbow crack tables are already precomputed, and are available for download...somewhere.  Rainbow crack claims that it can crack up to 14 character passwords in alpha numeric in a minute or two with 99.9% probability of success.  I've never seen it done, but i suppose it does what they claim.

Ophcrack is another RainBow table generator, both are very effective. Typically with a sniffed windows challenge response you see the LM and NTLM versions of the password, LM is all uppercase, and NTLM (and ntlmv2) are case sensitive. LM limits you to 14 char's, but it's actually 7, two 7 character passes. Ntlm support up to 127 character's in upper/lower cases.

RainbowCrack is sort of unique in that, if a password is 14 char's or less, and both LM and NTLM part's of the pass are supplied (like in a pwdump, or ntdump of the SAM) then rainbowcrack looks at the LM pass first, once it's found both halves of the pass, then it take the two together and tries different cases trying to match the NTLM pass.

ThisIS_an_NTLM                  ....  NTLM pass's are case sensitive
THISIS_   (break)   AN_NTLM       .... LM passes aren't, and are actually two 7 characater passes combined

So RC will find the THISIS_ portion, and the AN_NTLM portion, then combine the plain-text back into THISIS_AN_NTLM then start to encrypt it into NTLM, trying different cases until the hashes match.

So if you do get RC or OC running, most of the time you don't have to generate the tables for NTLM for characters 1-14. If you get both hashes at the same time(most of the time), then why bother. FYI all characters, a-z,  0-9 space, and specials (less alt codes) for LM will make 64gig's of Rainbow tables... 1-7 only, all uppercase, sooo generating NTLM with it's case sensitivity would be a tremendious amount of data.

If you wanted to generate NTLM pass's I'd start at 15-20 characters... that would take a very very long time to even get 15 alone.

Both OC and RC work great.
-rich