[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6bc868ab8f0be0e92a927e31ce289d79@smtp.hushmail.com>
Date: Sun, 8 May 2016 11:13:22 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Using --show with older pot files
On 2016-05-08 03:20, Matt Weir wrote:
> I have a number of old pot files. When using them in a new cracking session
> they work great and john doesn't try to re-crack old passwords. I encounter
> problems though when I use the -show option to see how many passwords are
> cracked. Note, this is using bleeding john.
>
> '--show=left' works as expected with old pot files. Old hashes are matched
> as having cracked passwords in the list
>
> '--show' only shows passwords cracked with newer cracking sessions, not
> ones cracked under the older style pot files.
>
> For example, assume the following pot file, (hashes x'd out)
>
> XXXXXXXXXXXXXXXXXXXXXXX:password1
>
> $dynamic_0$XXXXXXXXXXXXXXXXXXXXX:password2
>
> If I run ./john -show target_list
>
> 2:password2
>
> 1 password hashes cracked, 1 left
>
> Even though password1 is in my cracked list and target list. Aka if it
> doesn't have the $hashtype$ in front it doesn't work with the --show option.
Are you seeing this with formats other than dynamic? We probably have
several formats with this problem but anyway it's a per-format issue
(and many formats, especially non-hashes, are not supposed to recognize
bare hashes anyway). It's usually a result of using prepare() for things
that should be put in split():
https://github.com/magnumripper/JohnTheRipper/wiki/split()-vs.-prepare()
We should basically only use prepare() for its initial reason to exist,
namely for reading other input fields than the ciphertext. Good examples
are for reading pwdump or l0pthcrack formats.
magnum
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.
