Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 22 Sep 2011 19:36:28 -0600
From: Stephen John Smoogen <>
Subject: Re: John the Ripper 1.7.8-jumbo-7

2011/9/22 Solar Designer <>:
> On Wed, Sep 21, 2011 at 04:27:07PM -0600, Stephen John Smoogen wrote:
>> On Wed, Sep 21, 2011 at 14:35, Solar Designer <> wrote:
>> > * More character encodings are now supported.  The full list is: raw,
>> > utf-8, iso-8859-1, iso-8859-7, iso-8859-15, koi8-r, cp437, cp737, cp850,
>> > cp858, cp866, cp1251, cp1252, cp1253.
>> > * Full encoding support for "single crack" mode, rules, and character
>> > classes has been implemented. (JimF/magnum)
>> Does this work with incremental mode?
> No.  Incremental mode is unaware of character encodings.  With
> incremental mode, the candidate passwords produced are based on whatever
> octets were seen in sample passwords in john.pot from which .chr files
> were generated, additionally limited to the CHARSET_MIN to CHARSET_MAX

Ah so I guess I have been running up against CHARSET_MIN/MAX  in my
previous tests. In the integer based calculations, I think  that if
one wanted to make larger lengths, you needed to minimize the
charsets. Which if I remember correctly to say make it from 32->126 to
32->255 the length would need to decrease by an amount to keep it from
overflowing (length 5 off the top of my head.)

Thanks for the rest of the explanation, it clarified other questions I had.

Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren

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.