[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <437B02A0.7050003@banquise.net>
Date: Wed, 16 Nov 2005 10:57:52 +0100
From: Simon Marechal <simon@...quise.net>
To: john-users@...ts.openwall.com
Subject: Re: Speed up John
Michael Behrisch wrote:
> 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 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 would be O(number_of_keys_tried). When you want to crack password 10M
to 11M, you'll have to generate 10M canditate passwords.
A workaround would be not to stop john -stdout at the end of cracking.
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.
