Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKGDhHVPqrc+Tma4YkjbURdWGk1qpKamEhxRB8x5EnF_7wdtfg@mail.gmail.com>
Date: Sat, 4 Apr 2015 21:08:53 +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-04 16:52 GMT+02:00 Frank Dittrich <frank.dittrich@...lbox.org>:
>Unless you implement tunable cost reporting for pomelo and use --cost=,
>--test will check whether all the tests pass, and then use just the
>first two tests to compute the performance.

I've discovered that --cost modifies also fmt_test structure in fmt_main
(but only with the --test flag!). I can take advantage of this.
previously I was debuging without the --test flag and I saw that first
are executed init() and reset() and after them functions tunable_cost_*.

If I change one hash in fmt_test to a wrong one
I have
./john --test --format="django-scrypt" --cost="14,8,1"
Speed for cost 1 (N) of 14, cost 2 (r) of 8, cost 3 (p) of 1
Raw:    403 c/s real, 14.0 c/s virtual

./john django --format="django-scrypt" --cost="14,8,1"
Self test failed (cmp_all(1))

It's a bug? (auto tune for all hashes)

Content of type "text/html" skipped

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.