[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20051116100145.GA10479@openwall.com>
Date: Wed, 16 Nov 2005 13:01:45 +0300
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: Speed up John
On Wed, Nov 16, 2005 at 10:26:17AM +0100, Michael Behrisch wrote:
> Am Mittwoch, 16. November 2005 10:09 schrieb Solar Designer:
> > "john --stdout" would require more bandwidth and would not scale too
> > well, though, -- but it's fine for the slower hashes and for not too
> > many nodes.
>
> No, my idea was to use john --stdout on the client side. The setup would be
> as follows. The client connects to the server and says "ready to crack".
> The server says OK, please take password 1000 to 2000, the client runs
> john --stdout, throws away the first 1000
What if it would need to throw away the first billion of candidates
once those have already been tried?
> and feeds the next 1000 into
> john --stdin and then responds OK to the server which gives the next
> share and so forth. The server needs to know nothing about john, it just gives
> the numbers which is very low bandwidth. This would also scale easily.
It really won't work well.
Approaches like that do require messing with John internals (for purists:
"john.rec" files fall into the same category, but a source code patch
works much better).
--
Alexander Peslyak <solar at openwall.com>
GPG key ID: B35D3598 fp: 6429 0D7E F130 C13E C929 6447 73C3 A290 B35D 3598
http://www.openwall.com - bringing security into open computing environments
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.
