Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 21 Mar 2012 13:27:27 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: raw-MD5 bug (john.pot loading) in latest git

On 03/20/2012 11:48 AM, magnum wrote:
> On 03/20/2012 11:16 AM, Raphaƫl Rigo wrote:
>> Hello,
>> there's a bug with raw-MD5 and john.pot in latest git :
>>
>> $ cat coin
>> test:098f6bcd4621d373cade4e832627b4f6
>>
>> $ cat testpot
>> 098f6bcd4621d373cade4e832627b4f6:test
>>
>> $ ./john --pot=/tmp/testpot --format=raw-md5 /tmp/coin
>> Loaded 1 password hash (Raw MD5 [SSE2i 12x])
>> No password hashes left to crack (see FAQ)
>>
>> $ ./john --pot=/tmp/testpot --format=raw-md5 --show /tmp/coin
>> 0 password hashes cracked, 1 left
>>
>> if testpot is empty, john fills it with :
>> $dynamic_0$098f6bcd4621d373cade4e832627b4f6:test
>>
>> so it seems there's bug with pot loading. it is also buggy with
>> "generic" target.
> 
> This might be a bug, and it's a problem if you have old (pre
> 1.7.8-jumbo8 or so) untagged entries in the pot file.
> 
> It might have "happened" here:
> http://www.openwall.com/lists/john-dev/2011/10/24/10 but it was supposed
> to read bare (old) hashes from the pot file, but always store new ones
> with tags.

The above apparently has nothing to do with it, and this problem is not
format specific (it happens with untagged NT hashes too for example).
This is only a problem with -show, everything else works as it should.

This is a problem in 1.7.8-jumbo-8 and later, I haven't tried older
versions. I'm not quite sure what to do about it, or why it happens.
When loading for cracking or -show=left, hash is rejected as already
cracked (i.e. correct behavior). But when doing -show, hash is
considered not cracked. I can't see why! I'm giving up for now.

magnum

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.