[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP29484CEF2C41D6DE247A097FD2D0@phx.gbl>
Date: Tue, 15 Jan 2013 22:50:26 +0100
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: --list=<conf section name>
On 01/15/2013 10:40 PM, magnum wrote:
> On 15 Jan, 2013, at 22:27 , Frank Dittrich <frank_dittrich@...mail.com> wrote:
>> Another bug might be this one:
>> (unstable-jumbo)run $ ./john --list=parameters:options:mpi
>> mpiompverbose = Y
>> mpiompmutex = Y
>> (unstable-jumbo)run $ echo $?
>> 0
>> (unstable-jumbo)run $ ./john --list=parameters:options:opencl
>> (unstable-jumbo)run $ echo $?
>> 0
>>
>> May be $? should be != 0 here.
>> Or may be it should be 0 here, because [Options:OpenCL] exists, but it
>> should be != 0 here (section doesn't exist):
>> (unstable-jumbo)run $ ./john --list=parameters:options:none
>> (unstable-jumbo)run $ echo $?
>> 0
>> or here (Section contains list data):
>> (unstable-jumbo)run $ ./john --list=parameters:list.rules:single
>> (unstable-jumbo)run $ echo $?
>> 0
>
> Ah yes, this is relevant for things like Johnny. I'm not sure how a developer of things using this "interface" would want it, but I assume some of those cases should return non-zero.
Actually, when I added this stuff, I had the (yet to be built)
"automatic collaboration tool" for cracking passwords with a team of pen
testers in mind.
(Extracting a minimal config from the machine where a new session is
defined, storing it on a central server, distributing it to the next
machine which starts this specific cracking task...)
I doubt that this specific --list= functionality is useful for Johnny
(other --list= functionality is useful, once Johnny gets enhanced to
support jumbo editions).
Frank
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.
