Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62adc8110601182342i2742c027p5976f8f24a85b143@mail.gmail.com>
Date: Thu, 19 Jan 2006 13:12:57 +0530
From: bakul patel <bakulmech@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Incremental Alpha Quagmire

On 1/19/06, Arias Hung <arias@...-g.net> wrote:
>
> Another characterstic of JTR that I'm trying to wrap my mind around that
> doesn't seem to me to be quite optimal
> ... perhaps someone can point to the proper way to optimization in this
> case.
>
> When configuring the conf file, the incremental for alpha is defined as:
> (in my case I know the pw length that i'm attempting to decrypt)
>
> [Incremental:Alpha]
> File = $JOHN/alpha.chr
> MinLen = 8
> MaxLen = 8
> CharCount = 26
>
>
>
> What is baffling to me is the charcount, since it's listed as only 26 yet
> alpha passwords seem always to be a mixture of upper and lowercase.
>
> Should not the character count be 52?!?!
>
> Also, it seems to take an exorbitant amount of time before john begins
> attempting mixed (upper + lower) Alpha combinations.
>
> What would be the ideal way to get the upper/lower combinations to begin
> immediately?  Wouldn't it be ideal to increase character count to 52 and
> consider upper and lower to be separate character types as they certainly
> are treated as distinguished from one another as all passwords are case
> sensitive?
>
>
>
>

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.