Date: Tue, 01 Nov 2011 22:16:35 +0100 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: md5_gen tagging 2011-11-01 20:24, jfoug wrote: > This has now been changed in patch 0037. This was not a trivial change. Quite a bit had to be addressed. > > The new functionality, a format like raw-md5 (or dynamic_0) will detect any of these 'forms' > > $dynamic_0$HEX_32 > HEX_32 > md5_gen(0)HEX_32 > > It will use any of those forms as input, .pot file data, etc. Also, either format (raw-md5 or dynamic_0) will output $dynamic_0$HEX_32 to the john.pot file (for newly found items). > > > Note, there 'are' some side effects. > > 1. I had to re-order linkage of dynamic formats, ahead of any that use them (i.e. the #include was put after the dynamic linkage). > 2. More input files will list 'multiple' possible format warning. Any input file with $dynamic_0$ $dynamic_6$ $dynamic_9$ $dynamic_17$ $dynamic_29$ will all list multiple formats, if no specific -format=XX line was used. This is due to the thin format, AND the dynamic format matching. > 3. The thin formats required some changes, and some additional logic. Now, any format that has a 'more complex' line, than a straight hash, will have to have a split function added. This split is really thin. It simply calls the 'convert', and then calls the split function of dynamic (similar to C++ inheritance, which is how the 'thin' format has been modeled) > > This has been tested with the test suite. That helped flush out a lot of issues, that showed up, due to the changes. A lot of the problems were due to some global stuff in the dynamic format, AND the changes to john to 'show' the multiple/ambiguous formats which could also handle the input file. > > Jim. Great! I'll try it out. Maybe we can find a way to mute the format warnings in these cases. 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.