[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060408012828.GA20672@openwall.com>
Date: Sat, 8 Apr 2006 05:28:28 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: john won't load hash file...
On Fri, Apr 07, 2006 at 04:58:53AM -0400, Dan Baker wrote:
> ./john -format=MD5 passwd.txt
>
> I get:
>
> No password hashes loaded
>
> I have a MD5 hash that I am trying to put into the correct format.
> The total contents of the passwd.txt file is
>
> login:97c8e6d0d14f4e242c3c37af68cc376c
This is the correct format. However, this looks like a hex-encoded raw
MD5 hash. Out of the box, John supports only FreeBSD-style MD5-based
crypt(3) hashes, which are very different. Hex-encoded raw MD5 support
for John is available with a contributed patch - or you can just use the
jumbo patch which includes this functionality too.
> I also tried:
>
> login: username hash:97c8e6d0d14f4e242c3c37af68cc376c
>
> And
>
> hash:l97c8e6d0d14f4e242c3c37af68cc376c
These are wrong.
> I'm using the OS X version of John if that matters.
Well, you'll need to pick the source code distribution plus a suitable
patch (either the raw MD5 support patch or the jumbo patch) and build
from source (with the macosx-... "make" target that matches your system).
P.S. You do not need to specify the "--format" explicitly. In fact,
it's better to not do that, letting John autodetect the hash type for
you (out of ones supported in the given build of John). This option
should only be used when there are multiple hash types present in the
password file(s) that you pass to John.
--
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598 fp: 6429 0D7E F130 C13E C929 6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments
Was I helpful? Please give your feedback here: http://rate.affero.net/solar
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.
