Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 16 Nov 2005 09:54:42 +0100
From: Michael Behrisch <>
Subject: Re: Speed up John

Am Dienstag, 15. November 2005 21:49 schrieb Solar Designer:
> On Mon, Nov 14, 2005 at 11:48:33PM +0100, kraeh! wrote:
> > If you really want to speed up john, you should use more than just one
> > computer for it.
> > JohnNet is a quite nice tool for this. and i don??t say things like this
> > because i made it 8-)
> I had a look at this:
> Basically, this suffers from the same problem that dJohn and most other
> similar hacks do.  Unlike John the Ripper itself, these programs or John
> patches would not try candidate passwords in an optimal order.  As a
> result, John running on a single CPU for one day might crack more
> real-world password hashes than dJohn or JohnNet running on 10 CPUs
> would.

I don't know anything about the way those tools generate their 
(packages of) candidate passwords,
but if they use john --stdout to generate them, your objections
would not apply, would they?


Michael Behrisch (Tel. +49 30 2093-3123)
HU Berlin, Institut fuer Informatik, Arbeitsgruppe Algorithmen

Content of type "application/pgp-signature" 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.