[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 24 Mar 2011 05:31:49 +0300
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: single mode
On Wed, Mar 23, 2011 at 02:07:41AM +0100, magnum wrote:
> On 2011-03-22 23:35, Solar Designer wrote:
> > * Word separator characters for ldr_split_words(), used on GECOS fields.
> > */
> >#define issep \
> > "!\"#$%&'()*+,-./:;<=>?@[\\]^_`{|}~\177"
>
> Those plus the space. The difference in practice is a thing I neglected:
> It does support any "high" (8-bit) characters in the words, inherently
> including any UTF-8 encoded non-ascii.
Yes, that's what I meant (and I forgot to mention the space).
> >And then there's this check in single.c:
> >
> > c = (unsigned int)first->data[0] | 0x20;
> > if (c < 'a' || c > 'z') continue;
>
> I don't understand the surronding code fully. My previous statement was
> false: A word *can* start with a digit but a word consisting of just
> digits will not be paired.
Not exactly: it won't be the first word in a pair, but it can be the
second. For example, "abc 123 456" in the GECOS field results in:
abc
abc123
a123
abc456
a456
123
456
> Is that what the above line is about?
Yes. This check is in the word pairing context.
> Then how come a word with no 7-bit chars will be used, *and* paired?
Not as the first word in a pair. Maybe this needs to be changed or made
configurable.
> I know I
> can crack foreign passwords completely lacking ascii, with single user
> mode and the test words put in the GECOS field.
Sure, without word pairing.
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.
