[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 6 Jun 2012 17:51:32 -0400 (EDT)
From: "Brad Tilley" <brad@...ystems.com>
To: john-users@...ts.openwall.com
Subject: Re: pot file size limit
> On Tue, Jun 05, 2012 at 09:24:38PM -0400, Brad Tilley wrote:
>> Perhaps it's just me, but the biggest draw-back to using a large pot
>> file
>> seems to be the load time. Once the pot is greater than 1 gibi, the
>> slowdown really feels substantial. However, this may just be my
>> perception
>> of time. In wall clock time, it takes just about 10 seconds to crack
>> hundreds of thousands of raw-md5 hashes, but about 2.5 minutes for John
>> to
>> start-up with such a large pot.
>
> Understood. Startup time mostly matters if you frequently interrupt and
> restart John or run it with small wordlists, etc. - but this is in fact
> reasonable use of it in some cases. So this is a valid concern.
Looping over the split hashes is one way to process the 130 million plus
raw-md5 hashes. Do you recall the swapping thread recently when a john
user attempted to load all 4+ gibi of hashes at once
(http://www.openwall.com/lists/john-users/2012/04/12/1)? When looping,
john starts and stops for each hash file.
One may also wish to loop, not over different hash files, but different
wordlists too.
for f in $(ls hashes/x*); do ./wm --pattern CVCCVC | john --pipe
--pot=big.pot --format=raw-md5 --nolog $f; done
> You could want to try increasing PASSWORD_HASH_SIZE_FOR_LDR from 4 to 5.
> Does this help?
I'll try that if time permits.
> Alexander
>
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.
