Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Aug 2012 08:54:28 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Output for dynamic formats in --list=format-details
 (and --list=format-all-details

On 08/02/2012 12:28 AM, jfoug wrote:
>> From: Frank Dittrich [mailto:frank_dittrich@...mail.com]
>> BTW: What change would be needed to make the following command test
>> valid() for dynamic formats as well?
>>
>> $ ./john hashes-all.txt-1.mscash2
>> Warning: detected hash type "lm", but the string is also recognized as
>> "lotus5"
>> clip.....
> 
> I do not think dynamic checks for 'raw' hashes, without being forced to.
> The problem with dynamic, is that for every raw hash, it will simply match
> almost every single dynamic.
> 
> Yes, we could change that, but why?  That would be MUCH more confusing than
> it is today.

There are some cases where I would love to see dynamic as well, e.g, if
I am not sure I am using the right format, or if no hashes are loaded,
but would be were dynamic included.

> TO make this happen, simply change this line, at the top part of
> dynamic_fmt.c (static data)
> 
>   // If we are run in 'specific' mode (say, -format=dynamic
> -subformat=dynamic_0, then we
>   // want to 'allow' raw hashes to be 'valid'. This is how we will do this.
> We have a boolean
>   // that if set to true, we will perform a 1 time check within the valid
> function. If at
>   // that time we find out that we are cracking (or showing, etc) that we
> will accept lines
>   // that are either format of $dynamic_0$hhhhhh...32 or simply in the
> format of hhhhhhh..32
> - static int m_allow_rawhash_fixup = 0;
> + static int m_allow_rawhash_fixup = 1;
> 
> This 'normally' gets set later on, in the part of code which prepares the
> array of
> format structures (in the dynamic_Register_formats() function).  Setting it
> to 1
> in the static data declaration, simply makes it turned on no matter what.

Perfect. let's make a config variable for it.

Frank



Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ