[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP300F7A7EB294195D112266AFDCF0@phx.gbl>
Date: Mon, 6 Aug 2012 19:44:19 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: johnny: progressbar's value and text
On 08/06/2012 07:21 PM, Aleksey Cherepanov wrote:
> Yes, I get my numbers from john --show. I just realized that they do
> not reflect overall progress for file. These numbers shows progress
> over one type of hashes in file (also I guess they are affected by
> options like --users). I do not know how to improve that. Do you see
> any better approach?
I'll have to check special cases like LM (passwords split into 2 halves)
and bigcrypt (special case of DES, supporting passwords longer than 8
bytes, which are split into 2 "halves" as well).
Otherwise, this should only be a problem if the input file contains
hashes of different formats or if the user somehow specified a format
which doesn't match the hashes in the file.
If you want to show global number of cracked passwords per file, even
for mixed formats, then you could run ./john --max-run-time=0, and parse
stderr for alternative formats which find valid hashes.
BUT:
This is IMO beyond the scope of GSoC.
For core john this shouldn't matter.
For jumbo, this doesn't take into account dynamic formats (currently,
all the dynamic formats are not tested when john tries to detect which
other formats find valid hashes in the input file. So, you'd have to
test each --dynamic format individually. But then you'll run into
problems because of ambiguous hashes.
Frank
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.
