[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E3795861-32A9-4462-8751-EFCA8877C3FA@gmail.com>
Date: Mon, 1 Jun 2015 13:52:58 +0800
From: Lei Zhang <zhanglei.april@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Interleaving of intrinsics
> On May 30, 2015, at 10:55 AM, Solar Designer <solar@...nwall.com> wrote:
>
> Lei wrote:
>> Somehow I couldn't get useful info from a forked run of pbkdf2-hmac-sha256/512. I used the same settings as I benchmarked raw-md4(5), but only got output like:
>> Will run 4 OpenMP threads per process (240 total across 60 processes)
>> Node numbers 1-60 of 60 (fork)
>> Session stopped (max run-time reached)
>>
>> I tried increasing --max-run , but to no avail. Something wrong here?
>
> I suspect max_keys_per_crypt might be too high. You'd want to find out
> what it was by examining the log file. It shouldn't actually be high
> for a slow hash like this, but maybe it is (and needs to be lowered).
It's 15360. This doesn't look insanely high to me.
> Also, you never mentioned your full command line. There might be
> something specific to the cracking mode you invoked and its settings.
I used the exact same settings as I benchmarked raw-md4, i.e.:
$ run/john --format=pbkdf2-hmac-sha256 --mask=?l?l?l?l?l?l?l?l --fork=60 --max-run=30 hash.sha256
Lei
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.
