[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP339BCFEBEB401D04A98AA94FDD20@phx.gbl>
Date: Tue, 10 Jul 2012 09:09:43 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Re: Aleksey's status report #10
On 07/10/2012 07:56 AM, Aleksey Cherepanov wrote:
> On Sat, Jul 07, 2012 at 11:57:53AM +0200, Frank Dittrich wrote:
>> On 06/27/2012 02:55 PM, Frank Dittrich wrote:
>>> For other section names, you might even need to implement new
>>> functionality to john, like listing the contents of a section (with
>>> include statements for sections or file names being resolved).
>>> Or at least functionality to get the value of a certain variable from a
>>> config section, so that you can parse
>>>
>>> File = $JOHN/my.chr
>>>
>>> and know which file is needed for that attack.
>>
>> It gets even more complicated, because default for --incremental is All,
>> except when you are cracking LM DES hashes.
>> For lm, the default is LanMan -> lanman.chr
>> (But we can also just assume that lanman.chr exists on all the clients.
>
> If we assume that .chr file(s) exists on all clients than we should
> check that it is the original file.
OK.
>>>From my point of view as a user it seems natural to replace original
> file with newly generated and probably adjust config a bit instead of
> adding a new section.
I think many users don't create new .chr files.
When I do, I always use new file names and new sections.
Frank
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.
