[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e4b1a5aefb7bc916112ebd05de68db09@smtp.hushmail.com>
Date: Mon, 25 Jun 2012 17:50:33 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Markov: allow start and/or end to be specified in
percent
On 2012-06-25 15:41, Frank Dittrich wrote:
> On 06/25/2012 02:26 PM, Frank Dittrich wrote:
>> Or should this idea be dropped, and I should allow
>>
>> --markov=[MODE:]LEVEL:START/END[:LEN]
>
> Thinking further, this would be unnecessary if --node=MIN[-MAX]/COUNT
> would be supported.
> I think that code is currently not even in bleeding.
> But was the code that broken that it wouldn't be a good addition for
> next jumbo?
> I know that --fork had problems, but --node?
AFAIK --node does not have any problems, in the contest tree it is
unified with the MPI code and fairly well tested. I could implement
--node for post-Jumbo-6 if people wants it (this will also automatically
split any other cracking mode for node x out of y)
The changes you propose will be a minor pain for me to merge with
magnum-contest and/or it will likely make implementing --node harder
(right now it would be very easy because I keep the contest tree up to
par with bleeding).
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.
