Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4a242a358386111b68976aa99f15c25@smtp.hushmail.com>
Date: Sat, 15 Sep 2012 11:11:40 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: "single crack" missing candidates (was: Office2john)

On 15 Sep, 2012, at 1:13 , Solar Designer <solar@...nwall.com> wrote:
> On Fri, Sep 14, 2012 at 11:22:53PM +0200, magnum wrote:
>> Is there any chance a very loaded GECOS field can "overwrite" the login field or otherwise screw Single mode from getting a candidate from that field?
> 
> Normally, no.
> 
>> I tried to spot any limitation on GECOS stuff other than LINE_BUFFER_SIZE but did not find any.
> 
> There are also LDR_WORDS_MAX and SINGLE_WORDS_PAIR_MAX, but they should
> not cause the behavior you're describing.

They do. Bumping LDR_WORDS_MAX from 0x10 to 0x20 fixes the problem in this case. Maybe because the correct password is just part of the username (delimited by underscores), not all of it?

Could we bump this value? We have an experimental version of office2john that rips things like Title, Subject, Author, Last Saved By, Template and Keywords from the document (these are readable even though the doc is encrypted) - and put into the GECOS field for use bu Single mode. Often, we get plenty of words so I think we might want to bump it to 0x40 or more, if it doesn't cause problems.

magnum

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.