[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5040e06bf16740a0257bed612005481d@smtp.hushmail.com>
Date: Mon, 19 Nov 2012 07:40:39 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: new fastssh format, please test and review
On 30 Oct, 2012, at 5:40 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
> On Tue, Oct 30, 2012 at 12:23 AM, magnum <john.magnum@...hmail.com> wrote:
>> On 29 Oct, 2012, at 16:14 , Dhiru Kholia <dhiru.kholia@...il.com> wrote:
>>
>>> By using the attached fastssh format, it is possible to get > 3X
>>> speedup over existing code (speedup is currently only for AES-128-CBC
>>> encrypted keys which are default these days on many systems).
>>>
>>> For some reason, benchmarking speed is very low. Actual cracking speed
>>> is nice :-)
>>
>> You have a similar "problem" with the Office format. The benchmark includes both AES and DES test vectors. If you comment the DES ones out, the speed will probably be accurate.
>
> I tried doing so. No luck.
>
> Maybe my verification checks are very expensive. If verification
> succeeds fully and too often (like it does in benchmarking) then the
> cracking speed might be too slow.
Try setting BENCHMARK_LENGTH to -1001 instead. This will benchmark using crippled plaintexts, (after a normal self-test) so avoids that problem.
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.
