[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23515ad5ddeaa77843bdd064a803f10c@smtp.hushmail.com>
Date: Sun, 9 Jun 2013 14:43:33 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Dyna renames (question)
On 9 Jun, 2013, at 14:39 , magnum <john.magnum@...hmail.com> wrote:
> On 9 Jun, 2013, at 14:31 , <jfoug@....net> wrote:
>> ---- magnum <john.magnum@...hmail.com> 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 like this, however, we also must address the -list=subformats, along with the benchmark screen output. I will start toying around with this, and see what comes of it. Lets NOT modify the bench-unify immediately, since the first round may not be the final.
>
> I just committed a change that just dropped the word "intrinsics" from all algorithm names (dynamic was affected through the use of shared headers). This change does not affect benchmark-unify though.
I will refrain from further such changes while you work on it. I might address specific non-dynamic formats though.
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.
