|
Message-ID: <1360952756.59763.YahooMailNeo@web140903.mail.bf1.yahoo.com>
Date: Fri, 15 Feb 2013 10:25:56 -0800 (PST)
From: deepika dutta <deepikadutta_19@...oo.com>
To: "john-dev@...ts.openwall.com" <john-dev@...ts.openwall.com>
Subject: Re: netntlm bitsliced conversion
Ok I will look into it. Just for your information, I am going offline for few days and won't be able to come here.
See you all soon :)
Cheers,
Deepika
________________________________
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Sent: Friday, February 15, 2013 6:53 PM
Subject: Re: [john-dev] netntlm bitsliced conversion
On 15 Feb, 2013, at 12:35 , deepika dutta <deepikadutta_19@...oo.com> wrote:
> > It is also an excellent example for future DES stuff. We should do the same to NETNTLM_old_fmt_plug.c for a starter - it is almost identical to MSCHAPv2. .
>
> I know it should be easier now to convert other formats too. I will look into this format and if it is almost similar to mschap, then probably it will get finished quickly.
Note that this too has a default format (netntlm, NETNTLM_fmt_plug.c) that exploits a weakness and does not need fast DES at all. The fallback format is where you'd use BS DES, it's netntlm-naive in NETNTLM_old_fmt_plug.c.
OTOH you could have a look at binary() in the "exploit" formats. That's where we brute-force the 2^16 possible block 3 DES keys from the NT hash. Maybe that could be done with BS? It would speed up loading a lot, but not actual cracking.
magnum
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.