Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091101220357055361.1fc551fd@gmail.com>
Date: Sun, 1 Nov 2009 22:03:57 +0100
From: websiteaccess <websiteaccess@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: JTR 1.7.3.4 with patches V2 - dict limits.

On Sun, 1 Nov 2009 22:39:59 +0300, Solar Designer wrote:
> On Sun, Nov 01, 2009 at 05:24:31PM +0100, websiteaccess wrote:
>>  I use the great 1.7.3.4 with jim's patches (v2).
>> 
>>  With very large dictionary (from 2 up to 7 gigas) I get the following 
>> error :
>> 
>>    ftell: Value too large to be stored in data type
> 
> This is the expected behavior for a 32-bit build of JtR when a wordlist
> exceeds 2 GB in size.  You need a 64-bit build for wordlists this large.
> 
> This was addressed on this mailing list before, including in response to
> a message of yours (W.A.) -
> 
> http://openwall.info/wiki/john/mailing-list-excerpts
> 
> * On wordlists larger than 2 GB requiring a 64-bit build of JtR (2009/02/19)
> 	http://www.openwall.com/lists/john-users/2009/02/19/3
>     * Mac OS X specific (2009/06/14)
> 	http://www.openwall.com/lists/john-users/2009/06/14/6
>     * On enhancing JtR to support Large Files on 32-bit (2008/12/09)
> 	http://www.openwall.com/lists/john-users/2008/12/09/2
> 
> Last time, you actually complained about not getting a "proper" error
> (like the one above), but getting improper progress reporting.  Maybe
> something got fixed in Mac OS X since then.  The behavior you're
> reporting now is more correct.
> 
> Of course, there's room for improvement of JtR itself, but nothing has
> been done on this, so whatever was said in the old postings referenced
> above still applies.
> 
> Alexander
> 

  JTR (raw-md5) compiled with macos X 64 is 2 times slower than macos X 
sse2


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.