[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150512114309.GA14261@openwall.com>
Date: Tue, 12 May 2015 14:43:09 +0300
From: Aleksey Cherepanov <lyosha@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: displaying full meta information about hashes with
--show=types
On Tue, May 12, 2015 at 10:01:56AM +0200, Frank Dittrich wrote:
> On 05/12/2015 09:52 AM, Aleksey Cherepanov wrote:
> >>> NT:0:1:0:$NT$0ed7dd550afb451ac5b94cb644310b09:
> >>> Raw-MD4:0:1:0:$MD4$0ed7dd550afb451ac5b94cb644310b09:
> >>> Raw-MD5:0:1:0:$dynamic_0$0ed7dd550afb451ac5b94cb644310b09:
> >>> Raw-MD5u:0:1:0:$dynamic_29$0ed7dd550afb451ac5b94cb644310b09:
> >>> ripemd-128:0:1:0:$ripemd$0ed7dd550afb451ac5b94cb644310b09:
> >>> Snefru-128:0:1:1::
> >>> NT-old:0:1:0:$NT$0ed7dd550afb451ac5b94cb644310b09:
> >
> > ^^
> > Each of these formats can load the hash
> > 0ed7dd550afb451ac5b94cb644310b09 .
>
> Obviously, dynamic_0 and dynamic_29 (and possibly other formats can also
> load this hash.
> These formats don't appear in that list, because of this default setting
> in john,conf:
Nice point!
> # if set to Y then dynamic format will always work with bare hashes.
> Normally
> # dynamic only uses bare hashes if a single dynamic type is selected with
> # the -format= (so -format=dynamic_0 would use valid bare hashes).
> DynamicAlwaysUseBareHashes = N
>
>
> Not sure if the possible dynamic formats should be added here, and how
> to do that without changing john.conf or trying each individual dynamic
> format.
There is an option to overwrite it:
--field-separator-char=C use 'C' instead of the ':' in input and pot files
Though neither the option nor the setting affect my code.
Thanks!
--
Regards,
Aleksey Cherepanov
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.
