Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 4 Jul 2012 00:03:07 -0700 (PDT)
From: deepika dutta <>
To: "" <>
Subject: Re: mschapv2 conversion

Hi, all

I found that for every first key (say X) in a bunch of 32 keys being read at a time, the test case having X as its key fails in first attempt but succeeds in second attempt (while running the command directly on john asĀ  ./john -ses=./tst -nolog -pot=./tst.pot -w:pw.dic '-form=mschapv2')

I have not yet found the reason causing this weird behaviour, something wrong is happening for every first key per set of keys read. I am looking into this problem... your comments will be useful.


 From: magnum <>
Sent: Tuesday, July 3, 2012 3:07 AM
Subject: Re: [john-dev] mschapv2 conversion
On 2012-07-02 22:26, deepika dutta wrote:
> Hi, I did the required changes and was testing using test suite, it
> succeeds for 1454 cases. When I run the command directly on john as
> follows:
> ./john -ses=./tst -nolog -pot=./tst.pot -w:pw.dic
> '-form=mschapv2'
> it succeeds for 1454 cases and on again running the command, it runs
> successfully for rest 46 cases..... So the problem is that certain
> cases are being skipped or not getting cracked in first attempt but
> crack on second attempt.... I am looking into this problem... are you
> aware of any reason may be causing it?

Run the code using the new "clang-debug" target in jumbo-6, or just use
Valgrind, and look for salt buffer overruns. That's just my first guess.

Other clues can be to watch the LAST cracked of the 1454, and look at
just where this password is located in pw.dic and which lines are
surrounding it. Are all the uncracked passwords later in the file than
that? Or are they scattered all over it? And the input file: which salts
are surrounding the last one cracked?

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.