Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Apr 2015 10:33:01 +0200
From: Agnieszka Bielec <bielecagnieszka8@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] John the Ripper support for PHC finalists

2015-04-01 19:48 GMT+02:00 Frank Dittrich <frank.dittrich@...lbox.org>:
>On 04/01/2015 06:56 PM, Agnieszka Bielec wrote:
>> there is a way to pass options by comand line somethig alike: -m_cost=x ?
>> I need it for the auto_tune and compiling the kernel.

>There is a --cost= command line option, see doc/OPTIONS
>The --cost option can be used in regular runs and with --test, as long
>as you have test vectors matching the requested cost settings.

>To use thze --cost option for pomelo, you need to implement reporting of
>the tunable costs.
>It is easy. See the django-scrypt format as an example.
>(bleeding-jumbo)JtR $ grep -A 5 "#if FMT_MAIN_VERSION > 11"
>src/django_scrypt_fmt_plug.c
>#if FMT_MAIN_VERSION > 11
>static unsigned int tunable_cost_N(void *salt)
>{
>       static struct custom_salt *my_salt;
>
>        my_salt = salt;
>--
>#if FMT_MAIN_VERSION > 11
>                {
>                        "N",
>                        "r",
>                        "p"
>                },
>--
>#if FMT_MAIN_VERSION > 11
>                {
>                        tunable_cost_N,
>                        tunable_cost_r,
>                        tunable_cost_p
>                },

thanks but it seems that first is executed init function (where I need
access to cost) before functions tunable_cost_*

[ CONTENT OF TYPE text/html SKIPPED ]

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ