Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 31 May 2006 11:04:54 +0100
From: Justin Clarke <justin@...tinclarke.com>
To: john-users@...ts.openwall.com
Subject: Re: Parallalizing John the Ripper

Hi,

If you are looking for beta testers once you get this stable, I am
interested.  I am currently running a (self) modified version of the
Ryan Lim MPI code on a Cray XD1 system (12 nodes, AMD Opteron x86-64),
and I would be interested in something usable in more than incremental
mode.

Thanks

Justin

On Wed, 2006-05-31 at 11:44 +0200, Otheus (aka Timothy J. Shelling)
wrote:
> On 5/31/06, Solar Designer <solar@...nwall.com> wrote:
> >
> > On Tue, May 30, 2006 at 03:33:37AM +0200, Otheus (aka Timothy J. Shelling)
> > wrote:
> > > My problem with john.pot getting corrupted was fixed by adding
> > -DOS_FLOCK to
> > > the CFLAGS for linux.
> >
> > That's weird, for two reasons:
> 
> 
> Make it three reasons.
> 
> I added -DOS_FLOCK to the linux-ppc64 make target, not the x86-64!!
> 
> 1. The default arch.h for sane platforms defines OS_FLOCK already.
> 
> 
> indeed.
> 
> 2. logger.c uses direct write(2) syscalls on pieces of data no larger
> > than POT_BUFFER_SIZE and consisting of a whole number of entries (no
> > partial lines).  The default POT_BUFFER_SIZE is 4 KB - the same as or
> > smaller than the page size on most architectures.  So even when OS_FLOCK
> > is not set, concurrent writes to john.pot by multiple instances of John
> > will most likely not result in john.pot getting corrupted.
> 
> 
> agreed.  Nevertheless, it WAS getting corrupted.   I will see if I can track
> it down in the next few weeks.
> 
> 
> 
> 
> 

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ