[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANWtx02jCtEhR4XrcfKgaPHd9GJi=2o1Z6GTWfrNCP1ZpkMB6Q@mail.gmail.com>
Date: Tue, 8 May 2012 12:05:04 -0400
From: Rich Rumble <richrumble@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: automation equipped working place of hash cracker, proposal
On Tue, May 8, 2012 at 11:55 AM, magnum <john.magnum@...hmail.com> wrote:
> I have half-heartedly maintained a private copy of the --fork and --node
> code, unified with the MPI code and with current git updates. It's not
> 100% complete but the idea was that a session started with --fork=4
> would produce .rec files that are identical to ones produced with
> mpiexec -np 4, so you could start a session using --fork and resume it
> under MPI, or vice versa.
>
> I'd like to finish that and release it but I don't have the inspiration:
> The problem is not so much writing the final pieces of code, as it is
> testing it :-/
I have linux and windows machines available, but other than compiling
and testing it against hashes on those two types of systems I doubt
I'd be of much help.
-rich
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.
