Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sun, 9 Jun 2013 19:23:52 +0200
From: magnum <>
Subject: Re: Dyna renames (question)

On 9 Jun, 2013, at 19:14 , <> wrote:
> ---- magnum <> wrote: 
>> On 9 Jun, 2013, at 14:31 , <> wrote:
>>> ---- magnum <> wrote: 
>>>> Solar moved the cracking algo into algorithm_name too, eg. [MD5 128/128 SSE2]. For dynamic, an option would be using the full algo spec for that, like this:
>>>> Benchmarking: dynamic_1: (joomla) [md5($p.$s) 128/128 SSE2].
> I made a very trivial change to dyna_fmt.c  The -list=subformats code was not changed at all. Only the benchmark was changed.  What I did was set the format_name to be "" (empty string), and moved the original string down into algorithm, along with the existing algorithm data.  Here are all of the dynamic benchmark strings.
> What do people think of this:
> Benchmarking: dynamic_0 [md5($p) (raw-md5) 128/128 SSE2 10x4x3]... DONE
> Benchmarking: dynamic_1 [md5($p.$s) (joomla) 128/128 SSE2 10x4x3]... DONE
> Benchmarking: dynamic_2 [md5(md5($p)) (e107) 128/128 SSE2 10x4x3]... DONE
> ...

IMHO ideally you should put the part within brackets as format_name but if that becomes non-trivial I guess we can live with this.

If you do that though, just drop the parens too. There will be a comma inserted iirc so it would look like this:

Benchmarking: dynamic_0, raw-md5 [md5($p) 128/128 SSE2 10x4x3]... DONE
Benchmarking: dynamic_1, joomla [md5($p.$s) 128/128 SSE2 10x4x3]... DONE
Benchmarking: dynamic_2, e107 [md5(md5($p)) 128/128 SSE2 10x4x3]... DONE


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.